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
Notice how the code has stealthily changed the type of the relation realization[CommunicationNetwork*ApplicationInterface] into realization[CommunicationNetwork*ApplicationComponent].
The concept ApplicationComponent is sandwiched between two other concepts
CLASSIFY ApplicationInterface ISA ApplicationComponent
CLASSIFY ApplicationComponent, ApplicationInterface ISA ArchiObject
I can sense a diagnosis coming up. I need to run some more tests to validate my hypothesis.
stefjoosten
changed the title
An enforcement rule produces a yellow violation
An automatic rule produces a yellow violation
Aug 28, 2023
What happened
I got a yellow error message:
I traced it back to the following code fragment:
I have checked that the relations mentioned in this rule exists:
The type checker accepted this rule, hence code was generated and the error could occur.
What I expected
Version of Ampersand that was used
The example used
Ampersandtarski/prototype-framework:v1.17
as a base container.The text was updated successfully, but these errors were encountered: