Skip to content

[1279] Display ViewUsages contents in diagrams#1282

Merged
AxelRICHARD merged 1 commit intomainfrom
fro/enh/view-usage-node-content
May 20, 2025
Merged

[1279] Display ViewUsages contents in diagrams#1282
AxelRICHARD merged 1 commit intomainfrom
fro/enh/view-usage-node-content

Conversation

@frouene
Copy link
Contributor

@frouene frouene commented May 7, 2025

Bug: #1279

PLEASE READ ALL ITEMS AND CHECK ONLY RELEVANT CHECKBOXES BELOW

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 + doc/content/modules/user-manual/pages/release-notes/YYYY.MM.0.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?
  • Are the new / upgraded dependencies mentioned in the relevant section of the CHANGELOG.adoc + 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.

@frouene
Copy link
Contributor Author

frouene commented May 7, 2025

I have some tests to add

@frouene frouene force-pushed the fro/enh/view-usage-node-content branch from 011fc34 to bc5d0f9 Compare May 12, 2025 11:21
@frouene
Copy link
Contributor Author

frouene commented May 12, 2025

Tests added

@frouene frouene force-pushed the fro/enh/view-usage-node-content branch 2 times, most recently from af472d8 to 8d6e8fd Compare May 20, 2025 06:11
@AxelRICHARD AxelRICHARD force-pushed the fro/enh/view-usage-node-content branch from 8d6e8fd to c1ea882 Compare May 20, 2025 07:36
Bug: #1279
Signed-off-by: Florian ROUËNÉ <florian.rouene@obeosoft.com>
@AxelRICHARD AxelRICHARD force-pushed the fro/enh/view-usage-node-content branch from c1ea882 to 0c07fe4 Compare May 20, 2025 08:06
@AxelRICHARD AxelRICHARD merged commit 41673d2 into main May 20, 2025
4 checks passed
@AxelRICHARD AxelRICHARD deleted the fro/enh/view-usage-node-content branch May 20, 2025 08:29
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.

2 participants