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

Omitting startrule doesn't fallback to first parser rule (when debugging) #87

Closed
ronnieoverby opened this issue Aug 4, 2019 · 1 comment
Closed
Assignees
Labels
bug

Comments

@ronnieoverby
Copy link

@ronnieoverby ronnieoverby commented Aug 4, 2019

As the title says, I must supply a start rule in launch.json or else I get an error stating that undefined rule can't be found.

Your docs state that the first parser rule will be used in the absence of a specified start rule.

@ronnieoverby ronnieoverby changed the title Omitting startrule doesn't fallback to first parser rule Omitting startrule doesn't fallback to first parser rule (when debugging) Aug 4, 2019
@mike-lischke mike-lischke self-assigned this Aug 5, 2019
@mike-lischke mike-lischke added the bug label Aug 5, 2019
@ronnieoverby

This comment has been minimized.

Copy link
Author

@ronnieoverby ronnieoverby commented Aug 5, 2019

Let me know if you need anything from me to reproduce this. As a workaround, I've set the start rule to "debug" and just have a debug rule in my grammar that aliases the rule that I want to test.

mrd1996 added a commit to mrd1996/vscode-antlr4 that referenced this issue Oct 26, 2019
mike-lischke added a commit that referenced this issue Oct 26, 2019
Fix bug on issue #87
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.