Add line, column, and index numbers to nodes #90
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
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.
Fixes #89
This adds the start and end positions of nodes to the parsed output if specified by the new parse option
includePositions: true, which by default isfalse.Existing programs will be unaffected as this is an opt-in feature. However, there are a couple of bug fixes that these changes brought to light, which should benefit everyone.
One reason for the opt-in nature of this feature is the increased size of output. I know some developers store parsed HTML output for later processing and their current programs would not benefit from the position information and 2x storage costs is not ideal.
The demo page now has
includePositionsand strip white-space toggles.