-
-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Generated dependent grammar selects incorrect entry rule #4
Comments
Is I think it would be a nice fragment option to force-generate overridden rules in super grammars. |
Yes, |
@steve-hickman-epistimis I think it would be better to just generate duplicates to see the errors reported by Langium. See also #7 |
The challenge there is the usability of the net result. The base rules are defined in a published standard - so I don't have much room for modifications there - and changes to remove the overriding rules could make the net result less user friendly. |
Currently there is no way to directly override a super grammar rule.
I agree, I will set removing overridden rules to false by default. |
By default overridden rules will not be removed, but you will see an error in the sub grammar and need to resolve it. |
@steve-hickman-epistimis |
I have several XText grammars with dependencies as follows:
When I generate from the Privacy grammar, I get the following files:
The
Face.langium
grammar is generated like this (corrected for issues 2 & 3):However,
Face.xtext
is defined like this:Note that
ArchitectureModel
is the entry rule for theFace.xtext
grammar. It isn't even generated for theFace.langium
grammar.The text was updated successfully, but these errors were encountered: