-
-
Notifications
You must be signed in to change notification settings - Fork 187
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
Add ValueSpecificationAction #2601
Add ValueSpecificationAction #2601
Conversation
@sz332 Please review if this is what you desired and also whether it is conforming with standards - I think I got it right. But I failed to locate where this stereotype "valueSpecification" originates from because I could not find it from UML not that I started checking it, so it might be SysML exclusive thing, but I am not entirely sure. |
5c3f7cb
to
a18ec0a
Compare
I checked in the standard and various tools, and I think you got it right. The <> is according to my understanding is not a stereotype but a visual aid for modelers to see that this action is actually a value specification action. I have seen this behaviour in some tools, but there are some that use just a label Value specification without the stereotype notation. |
@danyeaw can you please review? From my point of view it is a good V1 feature, gets the job done for now. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like a valuable improvement 😉 .
@amolenaar Ah, I finally see what you did there! 😂 Nice one! |
gaphor/ui/icons/hicolor/scalable/actions/gaphor-value-specification-action-symbolic.svg
Show resolved
Hide resolved
a18ec0a
to
0ec9a25
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @marek-piirikivi!
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Issue Number: N/A
What is the new behavior?
Does this PR introduce a breaking change?
Other information