You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One thing that's nice about Chevrotain is the debugging experience. You can set breakpoints in VSCode and step through and see is it makes "decisions" about which path to take. WIth a relatively small lookahead, these are easy to grok.
However, I'm finding that with this lookahead strategy, it's much harder to discern why Chevortain didn't take a certain path. It would be nice if there was a way to log (or inspect?) why a subrule wasn't chosen or was determined not to match the input.
Is something like that possible?
The text was updated successfully, but these errors were encountered:
One thing that's nice about Chevrotain is the debugging experience. You can set breakpoints in VSCode and step through and see is it makes "decisions" about which path to take. WIth a relatively small lookahead, these are easy to grok.
However, I'm finding that with this lookahead strategy, it's much harder to discern why Chevortain didn't take a certain path. It would be nice if there was a way to log (or inspect?) why a subrule wasn't chosen or was determined not to match the input.
Is something like that possible?
The text was updated successfully, but these errors were encountered: