feat(Insomnia): clarify dynamic mocking and faker usage#4969
Open
juliamrch wants to merge 3 commits intorelease/insomnia-v12.6from
Open
feat(Insomnia): clarify dynamic mocking and faker usage#4969juliamrch wants to merge 3 commits intorelease/insomnia-v12.6from
juliamrch wants to merge 3 commits intorelease/insomnia-v12.6from
Conversation
juliamrch
force-pushed
the
insomnia-dynamic-mock-clarity
branch
from
00e33f0 to
06187df
Compare
✅ Deploy Preview for kongdeveloper ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
juliamrch
force-pushed
the
release/insomnia-v12.6
branch
from
57c0ccb to
adcfd35
Compare
juliamrch
force-pushed
the
insomnia-dynamic-mock-clarity
branch
from
06187df to
2335d8c
Compare
Contributor
There was a problem hiding this comment.
Pull request overview
Clarifies Insomnia’s Dynamic Mocking documentation by explaining how Liquid templates are rendered at request time, contrasting static vs dynamic mocks, and expanding guidance on faker variables.
Changes:
- Reworks the intro to describe request-time Liquid rendering and the kinds of dynamic data supported.
- Adds a table comparing static vs dynamic mocks and a short “how to” for configuring mock bodies.
- Expands faker variable guidance and adds an example using
fakerFunctions.
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Guaris
requested changes
Apr 23, 2026
| ``` | ||
|
|
||
| For a complete list of available faker variables, go to [**run.js#L218**](https://github.com/Kong/insomnia-mockbin/blob/04134cf81ce29ae7ffcc7ee13e2ecbce70414a96/lib/routes/bins/run.js#L218). | ||
| For a complete list of available faker variables, go to [**run.js#L218**](https://github.com/Kong/insomnia-mockbin/blob/04134cf81ce29ae7ffcc7ee13e2ecbce70414a96/lib/routes/bins/run.js#L218). Use the names listed under `fakerFunctions` (such as `guid`, `randomFullName`, `randomPhoneNumber`, etc.). For example: |
Contributor
There was a problem hiding this comment.
Thoughts about this:
- If this code gets moved around, line 218 could be line 318 one day and we wouldn't be aware of it/could be directing users to the wrong thing.
- No definition or curation to the variables, so for example, I have no way to know what this is used for or when to use it:
randomAbstractImage: () =>
faker.image.urlLoremFlickr({ category: "abstract" }),
I think if the list of variables is worth documenting, it should live in the docs. Maybe as an include files that gets pulled into this. And, then the variables could have some sort of description. Alternatively, curating some example variables and descriptions would work.
I think this is Postman's version of this info:
https://learning.postman.com/docs/tests-and-scripts/write-scripts/variables-list/
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
This PR clarifies the Dynamic Mocking features with:
Fixes #4965
Preview Links
Current docs VS. this PR
Checklist
descriptionentry in frontmatter.