-
-
Notifications
You must be signed in to change notification settings - Fork 216
Control visibility of requirements #3249
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
Control visibility of requirements #3249
Conversation
upon changing requirement text, id or toggling visibility of text
allowing different diagram properties for the same requirement, such as text visibility
covering use of button and auto-reset of height upon text change
hi @marek-piirikivi, I recently discovered gaphor and as an exercise to get to know this library a little better I picked up your feature request (given the first-timers-only flag)! I would love to here if this PR addresses your request adequately :). Many thanks in advance for your feedback. |
took example from BlockItem
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.
I had some questions while working on this PR, would be fantastic if someone could point me towards the answer
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.
This looks pretty good already. Really nice to see.
separate Requirement properties from RequirementItem properties
instead of earlier RESET_
Thanks a lot for the review @amolenaar! I believe I've processed all your comments :) |
Thanks @teunhoevenaars. The code looks really good and it works perfectly! @all-contributors: Add @teunhoevenaars for code. |
PR that addresses feature request to support controlling visibility of requirement's text
PR Checklist
Please check if your PR fulfills the following requirements:
Additionally:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Issue Number: #2967
What is the new behavior?
Does this PR introduce a breaking change?
hopefully not, but would love to hear your verdict :)
Other information