feat(JSON): operators possible in JSON strings #217
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
achenet
approved these changes
Sep 21, 2022
|
looks good to me :) |
maxatome
force-pushed
the
json-in-json
branch
7 times, most recently
from
b5e5d04 to
96e70bd
Compare
doc and examples done. |
maxatome
force-pushed
the
json-in-json
branch
2 times, most recently
from
87f3016 to
11cdfd0
Compare
- introduction of raw strings; - literal \n, \r & \t accepted in strings; - $^Operator(params...) is possible; - "$^Operator(params...)" is possible; - Operator (without parenthesis) is possible; - operator shortcuts reimplemented to not be handled specifically. Closes #203. Signed-off-by: Maxime Soulé <btik-git@scoubidou.com>
maxatome
force-pushed
the
json-in-json
branch
from
11cdfd0 to
75f91df
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
doc and examples are missing, but tests are OK