-
Notifications
You must be signed in to change notification settings - Fork 61
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/Bug: Disable cache for Parse Tree #264
Comments
Another thing: apparently the parse tree is already updating itself. But not the rules behind it. So as soon as I change the input file, the tree updates. but based on the opened grammar file. If I change the grammar file, it does not update. Even if I then change the input file, it still adopts the state from before the change in the Grammar file. |
I assume that after you change the grammar, you save it and start the debugging process again. You didn't mention these essential things, so I better ask. |
@mike-lischke Oh, right! Sorry that I gave you this information directly. But yes, I'll start the debugging process again. |
For further information, the other graphs are up to date: |
More information: |
I don't know if it might be due to a vscode update. But since I reported it here, it's just that the parse tree only updates if you restart vscode completely. (Version 1.88.1, system setup) |
Everything indicates that the internal grammar representation (ATN etc.) is not up to date. Needs investigation. |
I sometimes have the problem that the Prae Tree does not update. I have adjusted the rules but the parse tree does not update after "F5". Only a complete restart of vscode solves the problem. Is a cache to blame here? And would it be possible to simply have an option to deactivate it?
The text was updated successfully, but these errors were encountered: