Skip to content

[1237] Add support for ViewUsage in General View.#1238

Merged
AxelRICHARD merged 1 commit intomainfrom
fro/enh/view-frame-custom-node
May 6, 2025
Merged

[1237] Add support for ViewUsage in General View.#1238
AxelRICHARD merged 1 commit intomainfrom
fro/enh/view-frame-custom-node

Conversation

@frouene
Copy link
Contributor

@frouene frouene commented Apr 22, 2025

Bug: #1237

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 Apr 22, 2025
@AxelRICHARD AxelRICHARD linked an issue Apr 22, 2025 that may be closed by this pull request
@frouene frouene force-pushed the fro/enh/view-frame-custom-node branch from 627dec3 to d91f82b Compare April 29, 2025 12:55
@frouene frouene requested a review from AxelRICHARD April 30, 2025 13:37
@frouene frouene force-pushed the fro/enh/view-frame-custom-node branch 3 times, most recently from 7665642 to c5c54e6 Compare May 6, 2025 08:38
@AxelRICHARD AxelRICHARD force-pushed the fro/enh/view-frame-custom-node branch from c5c54e6 to acae111 Compare May 6, 2025 10:02
Bug: #1237
Signed-off-by: Florian ROUËNÉ <florian.rouene@obeosoft.com>
@AxelRICHARD AxelRICHARD force-pushed the fro/enh/view-frame-custom-node branch from acae111 to dd203f1 Compare May 6, 2025 10:40
@AxelRICHARD AxelRICHARD merged commit 4757dd7 into main May 6, 2025
4 checks passed
@AxelRICHARD AxelRICHARD deleted the fro/enh/view-frame-custom-node branch May 6, 2025 11:06
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.

Add ViewUsage as node in General View Diagram

2 participants