You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the docu we have "If there are multiple common rules than the first will be used as a result and the rest only for parsing".
Based on this sentence I tried:
Model: 'value' x=Base;
Base: S1|(S2 NotS3); // only use first rule (S2) as possible instance for each choice-option
S1: name=ID;
S2: name=ID;
NotS3: name=ID;
In this meta model Base should not be a base of NotS3... I think this is a possible issue (probably not so difficult to fix).
The text was updated successfully, but these errors were encountered:
I think you are right. It looks like a potential problem. The metamodel should be consistent with the parsing results. Since NotS3 instance is never instantiated during Base parsing (i.e. it will be thrown away after parsing) it shouldn't be its subclass.
Playing around with the meta model properties I added some tests: https://github.com/textX/textX/tree/feature/additional_metamodel_tests
I found a possible issue I would like to discuss:
In the docu we have "If there are multiple common rules than the first will be used as a result and the rest only for parsing".
Based on this sentence I tried:
In this meta model
Base
should not be a base ofNotS3
... I think this is a possible issue (probably not so difficult to fix).The text was updated successfully, but these errors were encountered: