Skip to content

Conversation

@pcdavid
Copy link
Contributor

@pcdavid pcdavid commented Jan 21, 2026

Bug: #1876
Signed-off-by: Pierre-Charles David [email protected]

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.

@AxelRICHARD AxelRICHARD added this to the 2026.1.0 milestone Jan 21, 2026
@AxelRICHARD AxelRICHARD linked an issue Jan 21, 2026 that may be closed by this pull request
@pcdavid pcdavid force-pushed the pcd/fix/npe-on-tree-item-delete branch from a017420 to 290281e Compare January 21, 2026 13:12
@pcdavid pcdavid force-pushed the pcd/fix/npe-on-tree-item-delete branch 2 times, most recently from 50f7eea to 605c389 Compare January 21, 2026 13:44
@AxelRICHARD AxelRICHARD force-pushed the pcd/fix/npe-on-tree-item-delete branch 2 times, most recently from dffbf08 to 35bef3a Compare January 22, 2026 08:11
@AxelRICHARD AxelRICHARD force-pushed the pcd/fix/npe-on-tree-item-delete branch 2 times, most recently from dfb81b1 to 690e0cc Compare January 22, 2026 12:14
@AxelRICHARD AxelRICHARD force-pushed the pcd/fix/npe-on-tree-item-delete branch from 690e0cc to 34bb63d Compare January 22, 2026 14:17
@AxelRICHARD AxelRICHARD merged commit 5bc388b into main Jan 22, 2026
4 checks passed
@AxelRICHARD AxelRICHARD deleted the pcd/fix/npe-on-tree-item-delete branch January 22, 2026 14:58
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.

Potential NPE in DeleteService.collectRelatedElements()

3 participants