Skip to content

Conversation

@adaussy
Copy link
Contributor

@adaussy adaussy commented Dec 23, 2025

Bug: #1738

PLEASE READ ALL ITEMS AND CHECK ONLY RELEVANT CHECKBOXES BELOW

Auto review

  • Have you reviewed this PR? Please do a first quick review, It is very useful to detect typos and missing copyrights, check comments, check your code... The reviewer will thank you for that :)

Project management

  • Has the pull request been added to the relevant milestone?
  • Have the priority: and pr: labels been added to the pull request? (In case of doubt, start with the labels priority: low and pr: to review later)
  • Have the relevant issues been added to the pull request?
  • Have the relevant labels been added to the issues? (area:, type:)
  • Have the relevant issues been added to the same project milestone as the pull request?

Changelog and release notes

  • Has the CHANGELOG.adoc + doc/content/modules/user-manual/pages/release-notes/YYYY.MM.0.adoc been updated to reference the relevant issues?
  • Have the relevant API breaks been described in the CHANGELOG.adoc?
  • Are the new / upgraded dependencies mentioned in the relevant section of the CHANGELOG.adoc?
  • In case of a change with a visual impact, are there any screenshots in the doc/content/modules/user-manual/pages/release-notes/YYYY.MM.0.adoc?
  • In case of a key change, has the change been added to Key highlights section in doc/content/modules/user-manual/pages/release-notes/YYYY.MM.0.adoc?

Documentation

  • Have you included an update of the documentation in your pull request? Please ask yourself if an update (installation manual, user manual, developer manual...) is needed and add one accordingly.

Tests

  • Is the code properly tested? Any pull request (fix, enhancement or new feature) should come with a test (or several). It could be unit tests, integration tests or cypress tests depending on the context. Only doc and releng pull request do not need for tests.

@adaussy adaussy marked this pull request as draft December 23, 2025 13:02
@adaussy adaussy force-pushed the ada/enh/1738 branch 3 times, most recently from bd90941 to d2b2590 Compare December 23, 2025 15:06
@adaussy adaussy changed the title (Draft) [1738] Handle ConnectionUsage as Edge in SysON [1738] Handle ConnectionUsage as Edge in SysON Dec 23, 2025
@adaussy adaussy marked this pull request as ready for review December 23, 2025 15:36
@adaussy adaussy force-pushed the ada/enh/1738 branch 3 times, most recently from 0a8e852 to dbc10d9 Compare December 29, 2025 08:42
@AxelRICHARD AxelRICHARD added this to the 2026.1.0 milestone Dec 30, 2025
@AxelRICHARD AxelRICHARD linked an issue Dec 30, 2025 that may be closed by this pull request
* collection of all {@link NodeDescription}
* @return the list of description representing usages
*/
public List<NodeDescription> getMainNodeDescriptions(List<NodeDescription> allNodeDescriptions, EClass type) {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't understand "main" here.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Main is to contract with "technical" Node description such as compartments.

What would you suggest ?

Copy link
Member

@AxelRICHARD AxelRICHARD Dec 30, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok I understand now.
After discussion let's try "getConnectableNodeDescriptions".

Bug: eclipse-syson#1738
Signed-off-by: Arthur Daussy <arthur.daussy@obeo.fr>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Handle ConnectionUsage as Edge in SysON

2 participants