Fix default matcher for box: match / for box only when it's a prefix for something #5
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.
Hi, first of all -- thanks for the great tool! Currently I'm migrating from
parcon.railroadtosyntraxfor my project's documentation (which involves a custom SQL dialect description).There is an issue #2 -- it's not only me who came across the difficulty to get
'/'node to be shown correctly as a simple token.Let me offer the better solution than it was discussed in the issue. Since
'/'-as-a-prefix should work only if something follows it, it seems that 'box' matcher should be fixed to^/., that is 'beginning of a string, '/', and at least one character more'. Then we save the same behaviour for the '/' prefix, except only for a case when it stands alone -- for whichtokenrule will work.