-
Notifications
You must be signed in to change notification settings - Fork 506
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
feat: unescape escaped characters when value is not quoted #421
feat: unescape escaped characters when value is not quoted #421
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This makes sense to me. @cadwallion, I'd love to hear your thoughts
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Apologies for the slow response, @bethesque, this looks great! Thank you for the bump @bkeepers.
Much appreciated! |
Is there an expected date for the next release? |
My plan is to review outstanding PRs/issues tomorrow and cut a release before the end of the day in the pacific timezone. |
Hi. I know it's been a while, but as far as I can tell, this was never released. We're currently pointing our gem source at a private repo for this feature, but would like to change that to use the public gem. Could this be released please? |
2.8.0 is out with this change. Sorry for the delayed release. Enjoy! |
Better late than never! 😆 Thanks! |
Thank you for this handy gem. We use it regularly.
When using Ruby's shellwords library to escape values, the following env file is created.
Quotes cannot be used around those values, otherwise the backslash is considered a literal.
This PR updates the code to correctly unescape characters when quotes are not used
The parse_value method had to be refactored to keep Rubocop happy.