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
Item constraint handling #145
Conversation
Then we no longer need to manage constraints in the item itself
Remove unused attributes from context
Now we can decouple canvas from view.
One step closer to a clean model.
Co-authored-by: Sourcery AI <>
Sourcery Code Quality ReportMerging this PR leaves code quality unchanged.
Here are some functions in these files that still need a tune-up:
Legend and ExplanationThe emojis denote the absolute quality of the code:
The 👍 and 👎 indicate whether the quality has improved or gotten worse with this pull request. Please see our documentation here for details on how these metrics are calculated. We are actively working on this report - lots more documentation and extra metrics to come! Let us know what you think of it by mentioning @sourcery-ai in a comment. |
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 is a smart refactoring to better separate the item constraints from the canvas!
Do we need to update the README and constraint.rst
, or would you prefer that we create a separate PR to update the docs with all the changes so far?
Good point. Let me do that in a separate PR, so I can first see what the impact of the changes in on Gaphor. |
PR Type
What kind of change does this PR introduce?
noapi changes)What is the current behavior?
Item specific constraints are managed in the item. Item needs a reference to a canvas to add/remove constraints to the constraint solver.
Issue Number: N/A
What is the new behavior?
Position
.Does this PR introduce a breaking change?
Other information