Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature request] Easier debugging #4

Open
matthew-dean opened this issue Aug 21, 2023 · 0 comments
Open

[Feature request] Easier debugging #4

matthew-dean opened this issue Aug 21, 2023 · 0 comments

Comments

@matthew-dean
Copy link

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant