Skip to content

[2085] Group diagrams by view definition in the Views Explorer#2086

Merged
AxelRICHARD merged 2 commits intomainfrom
fro/enh/views-explorer
Mar 20, 2026
Merged

[2085] Group diagrams by view definition in the Views Explorer#2086
AxelRICHARD merged 2 commits intomainfrom
fro/enh/views-explorer

Conversation

@frouene
Copy link
Contributor

@frouene frouene commented Mar 20, 2026

Bug: #2085

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.

@frouene frouene added this to the 2026.3.0 milestone Mar 20, 2026
@frouene frouene linked an issue Mar 20, 2026 that may be closed by this pull request
frouene and others added 2 commits March 20, 2026 17:56
Bug: #2085
Signed-off-by: Florian ROUËNÉ <florian.rouene@obeosoft.com>
Signed-off-by: Axel RICHARD <axel.richard@obeo.fr>
@AxelRICHARD AxelRICHARD force-pushed the fro/enh/views-explorer branch from 426868b to cbc6278 Compare March 20, 2026 17:01
@AxelRICHARD AxelRICHARD merged commit da8665d into main Mar 20, 2026
4 checks passed
@AxelRICHARD AxelRICHARD deleted the fro/enh/views-explorer branch March 20, 2026 17:51
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.

Adapt views exporer view to syson diagram

2 participants