Accept json grammars #3
Open
Conversation
This file contains hidden or 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
added 3 commits
May 4, 2016 01:35
This commit added support for generating parsers from a grammar provided in JSON format rather than just .jison format. Since a .jison grammar will never be valid JSON value, the plugin now checks if the input is JSON parseable, and if it is, treats it as JSON. Otherwise it will revert to its previous behaviour.
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.
This pull request adds support for generating parsers from a grammar provided
in JSON format rather than just .jison format.
Since a .jison grammar will never be valid JSON value, the plugin now
checks if the input is JSON parseable, and if it is, treats it as JSON.
Otherwise it will revert to its previous behaviour.
I also updated the dependencies.