fix(dev-env): key=value parsing
#2602
Merged
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.



Description
vip dev-env envvarcommands incorrectly display values containing the equal sign. This happens because the equal sign splits the key-value line, andsplit()in JavaScript behaves differently than in PHP ('x=a=b'.split( '=', 2 )will split the entire line by=, but will return only the first two items; while PHP in this case will split the line by the first=).This PR fixes that.
Changelog Description
Fixed
vip dev-env envvarcommands now correctly display values with embedded equal signs.Pull request checklist
New release checklist
Steps to Test
vip dev-env envvar set X 123==vip dev-env envvar get-allWithout this patch, the result will be
With this patch,