We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Given the ENV file below:
---env begins here---
APP_NAME=FooBar APP_COMM_CRED="[{"key":"foo"},{"key":"bar"}]"
---env ends here---
The JSON value of APP_COMM_CRED is deformed and the "key" attributes lose their double-quotes after performing the parse function.
APP_COMM_CRED
parse
The text was updated successfully, but these errors were encountered:
Interesting.
Seems that envfile should use https://github.com/bevry/normalify then.
Happy for you to send a PR.
I do have to merge #213 sometime as well.
Sorry, something went wrong.
@NamPNQ in your opinion, would https://github.com/bevry/normalify be suitable for this?
I think we can handle by just check value.startsWith() && value.endsWith() by double quote, or single quote, then we get substring of value
value.startsWith() && value.endsWith()
IMO, use this will make unexpected behavior, because env value is always is string, not number nor boolean
Successfully merging a pull request may close this issue.
Given the ENV file below:
---env begins here---
---env ends here---
The JSON value of
APP_COMM_CRED
is deformed and the "key" attributes lose their double-quotes after performing theparse
function.The text was updated successfully, but these errors were encountered: