[2013] Add a tool to create and setup a FlowUsage on a ConnectionUsage#2020
Open
[2013] Add a tool to create and setup a FlowUsage on a ConnectionUsage#2020
Conversation
e834485 to
e45b8e6
Compare
e45b8e6 to
a0cb411
Compare
Bug: #2013 Signed-off-by: Pierre-Charles David <pierre-charles.david@obeo.fr>
a0cb411 to
7aecb70
Compare
Member
|
@pcdavid please don't forget to auto-review your PR |
AxelRICHARD
reviewed
Mar 4, 2026
| ** Add _New Satisfy Requirement_ graphical edge tool between `Feature` graphical nodes and `RequirementUsage` graphical nodes. | ||
| This tool allows to create a `SatisfyRequirementUsage` between the `Feature` and `RequirementUsage` selected during the tool creation. | ||
| ** Add a _New Flow_ tool on `ConnectionUsage` graphical edges. | ||
| The tool allows to create and setup a `FlowUsage` with a `PayloadFeature` selected during the tool creation |
| return label.toString(); | ||
| } | ||
|
|
||
| public String getConnectionUsageLabel(ConnectionUsage element) { |
| return this.diagramQueryService.findNodeById(diagram, nodeId); | ||
| } | ||
|
|
||
| public boolean canCreateFlowUsage(ConnectionUsage connection) { |
| } | ||
|
|
||
| public boolean canCreateFlowUsage(ConnectionUsage connection) { | ||
| var optionalConnectionType = connection.getOwnedRelationship().stream() |
Member
There was a problem hiding this comment.
connection.getType() is not enough?
| return this.diagramQueryElementService.shouldRenderConnectorEdge(connector, sourceNode, targetNode, cache, editingContext); | ||
| } | ||
|
|
||
| public boolean canCreateFlowUsage(ConnectionUsage connection) { |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bug: #2013
Signed-off-by: Pierre-Charles David pierre-charles.david@obeo.fr
PLEASE READ ALL ITEMS AND CHECK ONLY RELEVANT CHECKBOXES BELOW
Auto review
Project management
priority:andpr:labels been added to the pull request? (In case of doubt, start with the labelspriority: lowandpr: to review later)area:,type:)Changelog and release notes
CHANGELOG.adoc+doc/content/modules/user-manual/pages/release-notes/YYYY.MM.0.adocbeen updated to reference the relevant issues?CHANGELOG.adoc?CHANGELOG.adoc?doc/content/modules/user-manual/pages/release-notes/YYYY.MM.0.adoc?Key highlightssection indoc/content/modules/user-manual/pages/release-notes/YYYY.MM.0.adoc?Documentation
Tests