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

fix: all unsettable properties are derived too #1904

Merged
merged 4 commits into from
Mar 13, 2018

Conversation

pvojtechovsky
Copy link
Collaborator

Examples are CtTypeReference#MODIFIER and COMMENT. Before they were derived==false unsettable==true. Now they are derived==true unsettable==true

WDYT?

@monperrus
Copy link
Collaborator

I agree, we have "unsettable implies derived" (but not the opposite, because we have derived setters).

do we check "unsettable implies derived" in a test ?

@pvojtechovsky
Copy link
Collaborator Author

do we check "unsettable implies derived" in a test ?

no. But how to do it?

It is interesting question, how to test that metamodel stuff at all...? It is somehow tested by other tests which are based on metamodel ... but it is secondary test. I have no idea how to write a primary test without increasing maintenance too much - by duplicate definition of metamodel data in test.

@monperrus
Copy link
Collaborator

It is interesting question, how to test that metamodel stuff at all...?

Simply like this?

for all metamodel classes:
   if a setter is @Unsettable then the corresponding getter is @Derived

@pvojtechovsky
Copy link
Collaborator Author

Tests was added. It is finished form my point of view

@monperrus monperrus merged commit e9f18c5 into INRIA:master Mar 13, 2018
@monperrus
Copy link
Collaborator

thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants