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.
This PR implements basic escaping support as implemented in the Ruby Gem
I have attempted to align the code style / logic components with the Ruby Gem.
Based on the assumption that this is the "source of truth" (pseudo spec) for this library.
I personally think other implementations of dotenv have more complete (better?) support for escaping and
expanding special characters (Example Spec).
But I wanted to start with the minimal viable scope and avoid misalignment with the "source of truth" (?)
resolves #711