[Feature Request] Add wildcard support for json files
See original GitHub issueHello,
it would be cool if the wildcard is passed into the json files to, so { id: __project_uuid__ }
will return the current uuid.
Maybe the wildcard needs some type of escaping, eg: $__project_uuid__$
This would reduce the usage of more complicated js files.
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
[feature request] json path support wildcard #4438 - GitHub
Expected behavior add build arg REPO_FROM to all artifact like patches: - op: add path: /build/artifacts[*]/docker/buildArgs value: ...
Read more >IAM JSON policy elements: Resource - AWS Documentation
Describes the Resource element of the IAM JSON policy language. ... The wildcards in the ARN apply to all of the following objects...
Read more >global.json overview - .NET CLI - Microsoft Learn
This field: Doesn't have wildcard support; that is, you must specify the full version number. Doesn't support version ranges.
Read more >JSON editing in Visual Studio Code
The file match syntax supports the '*' wildcard. Also, you can define exclusion patterns, starting with '!'. For an association to match, at...
Read more >Load JSON - APOC Extended Documentation - Neo4j
We can narrow down the data that we sift through and import using the JSON path syntax. This will allow us to specify...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
But
{"id": "__id__"}
would be already nice and I think its okay to turn it on by default, but maybe the user can disable it with an option passed to the mock configyeah you are right. Another cool thing would be usage of simple expressions
{ 'doubleID': 'mockExpresion(__uuid__ * 2)' }
where ‘mockExpresion’ indicates the value is an expression