-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature Request] Add wildcard support for json files #52
Comments
Hi, That's a good one. And also doesn't seem very difficult to implement. The most important part deciding a notation for variables in json files. I'll think about it. Any other suggestions and even PRs are very welcome. |
json needs for all keys/values strings, so maybe |
you are already introduced a wildcard notation with double underscore, so you probably fine using it again |
I'm not sure about "not using" quotes because in that case json files will be invalid and it can disturb people on editors or some linters. Maybe {
"id": "__id__"
} will be also good and safe enough. |
yeah you are right. Another cool thing would be usage of simple expressions
where 'mockExpresion' indicates the value is an expression |
But |
Hello,
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.
The text was updated successfully, but these errors were encountered: