-
Notifications
You must be signed in to change notification settings - Fork 420
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
Connect Reverse #427
Connect Reverse #427
Conversation
9e15903
to
e3d9bf6
Compare
I've added a few comments, hoping that they are useful. |
b786acc
to
fdd29c3
Compare
6ef97c7
to
c54a29a
Compare
There is test coverage missing in some path that seem to be relevant to new features you've implemented. Could you have a look and verify if that is the case? |
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.
Please decide whether to remove reconnect{START|END}
completely.
If we do that, clearly document it as part of the offending commit
BREAKING CHANGES:
* This happened, yo. Use strategy _X_ to migrate
Consider throwing descriptive errors if we remove API from modeling or make the legacy API work based on top of the new feature. If that is what we decide to do, we're going to keep around these bits forever maybe. Probably.
9603dc5
to
7472b5b
Compare
7472b5b
to
35d976f
Compare
954e9d2
to
cddefe5
Compare
cddefe5
to
e55d0eb
Compare
Connect and reconnect allow connections to be previewed and modeled in reverse order. To accomplish this rules will be checked for both (START -> END) as well as (END -> START). This feature comes with minor API reworks and must be supported downstream by updated Layouter implementation. * add Modeling#reconnect for reconnecting both source and target * Layouter#layoutConnection receives waypoints hint that needs to be taken into account to preview reverse connections BREAKING CHANGES: * connection.reconnectStart and connection.reconnectEnd rules are replaced with connection.reconnect rule * Connect context data changed { source, sourcePosition } -> { start, connectionStart }
* ensure connection preview works reversely
BREAKING CHANGES: * <connection.reconnectStart/End> commands removed * Modeling#reconnectStart/End still available for convenience
e55d0eb
to
b5b89bd
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.
Looking good.
🎉 |
Closes #386