Skip to content

Conversation

@frouene
Copy link
Contributor

@frouene frouene commented May 6, 2025

Bug: #1270

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 frouene added this to the 2025.6.0 milestone May 6, 2025
@frouene frouene linked an issue May 6, 2025 that may be closed by this pull request
@frouene
Copy link
Contributor Author

frouene commented May 6, 2025

I'll add appropriate tests when the ticket #1251 will be merged

Bug: #1270
Signed-off-by: Florian ROUËNÉ <florian.rouene@obeosoft.com>
@frouene frouene force-pushed the fro/enh/view-usage-as-representation branch from d336bdf to 696b454 Compare May 6, 2025 12:48
@frouene frouene marked this pull request as draft June 10, 2025 14:23
@AxelRICHARD AxelRICHARD removed this from the 2025.6.0 milestone Jun 10, 2025
@frouene
Copy link
Contributor Author

frouene commented Jun 10, 2025

Change to stand-by.
For the moment, the representation is present through a treeitem under the viewusage semantic object

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.

Link representation behavior to ViewUsage in explorer

2 participants