Skip to content

[1314] Update ViewUsage#exposedElement when manipulating GeneralView#1356

Merged
AxelRICHARD merged 2 commits intomainfrom
ari/enh/viewUsages
Jun 10, 2025
Merged

[1314] Update ViewUsage#exposedElement when manipulating GeneralView#1356
AxelRICHARD merged 2 commits intomainfrom
ari/enh/viewUsages

Conversation

@AxelRICHARD
Copy link
Member

@AxelRICHARD AxelRICHARD commented Jun 10, 2025

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.

@AxelRICHARD AxelRICHARD added this to the 2025.6.0 milestone Jun 10, 2025
@AxelRICHARD AxelRICHARD linked an issue Jun 10, 2025 that may be closed by this pull request
@AxelRICHARD AxelRICHARD force-pushed the ari/enh/viewUsages branch 2 times, most recently from 47d95b8 to e0b08ce Compare June 10, 2025 09:01
Bug: #1310
Signed-off-by: Axel RICHARD <axel.richard@obeo.fr>
@AxelRICHARD AxelRICHARD force-pushed the ari/enh/viewUsages branch 2 times, most recently from da1d947 to 2409487 Compare June 10, 2025 09:15
Bug: #1314
Signed-off-by: Axel RICHARD <axel.richard@obeo.fr>
@AxelRICHARD AxelRICHARD merged commit 5040de1 into main Jun 10, 2025
4 checks passed
@AxelRICHARD AxelRICHARD deleted the ari/enh/viewUsages branch June 10, 2025 09:55
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.

Update ViewUsage#exposedElement when manipulating GeneralView

1 participant