We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Moose entities have properties implemented in slots, for example:
FamixTMethod slots: { #parentType => FMOne type: #FamixTWithMethods opposite: #methods };
and other properties imlemented in their entityAttributes
entityAttributes
MooseEntity >> allTagAssociations <FMProperty: #allTagAssociations type: #FamixTagAssociation opposite: #entity ... ^ self attributeAt: #allTagAssociations ifAbsentPut: [ ... ]
when dealing with slots like in Orion, it is important to differentiate both because the first uses a slot and not the second.
I propose to put a new pragma that could be tested through a method in FM3Property
The text was updated successfully, but these errors were encountered:
proposed name for the pragma: <isExtension> ?
<isExtension>
Sorry, something went wrong.
No branches or pull requests
Moose entities have properties implemented in slots, for example:
and other properties imlemented in their
entityAttributes
when dealing with slots like in Orion, it is important to differentiate both because the first uses a slot and not the second.
I propose to put a new pragma that could be tested through a method in FM3Property
The text was updated successfully, but these errors were encountered: