-
Notifications
You must be signed in to change notification settings - Fork 67
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
Proposal missing from the content assist #1677
Comments
Hm, interesting. It's also pretty interest that this can be pretty easily fixed by using a small refactoring of the grammar. See here. |
Yes, in your refactoring, 'student' and 'teacher' are on different AstNodes, and it works properly. In my case, I think the issue comes from |
Yeah, I'm not saying that this isn't a bug - but there are at least in theory ways to circumvent this. I've added this to #1678. |
Thanks for the workaround. I continued investigating this issue and I noticed that we enter in this branch for the missing feature:
It means that the previous feature is added in the visited Set somewhere before processing the Group. |
Hey !
I probably found a minor issue in the content assist in case of multiple keyword alternatives. It seems that if the previous token is of a keyword kind, this keyword is not proposed by the content assist.
Langium version: 3.1
Package name: Langium
Steps To Reproduce
The current behavior
The content assist propose to create a new 'student' but not an other 'teacher'. After a 'student', the content assist propose to create a 'teacher' but not an other 'student'.
The expected behavior
The content assist should propose a 'student' and a 'teacher' in all cases.
The text was updated successfully, but these errors were encountered: