Skip to content

[2056] Fix feedback when dropping already exposed elements from the Explorer onto a diagram#2072

Open
pcdavid wants to merge 1 commit intomainfrom
pcd/fix/message-on-drop-visible-element
Open

[2056] Fix feedback when dropping already exposed elements from the Explorer onto a diagram#2072
pcdavid wants to merge 1 commit intomainfrom
pcd/fix/message-on-drop-visible-element

Conversation

@pcdavid
Copy link
Contributor

@pcdavid pcdavid commented Mar 17, 2026

Bug: #2056
Signed-off-by: Pierre-Charles David pierre-charles.david@obeo.fr

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.

@pcdavid
Copy link
Contributor Author

pcdavid commented Mar 17, 2026

I'm working on completing the scenarios tested by GVDropFromExplorerTests.

@pcdavid pcdavid force-pushed the pcd/fix/message-on-drop-visible-element branch from 1a9fa06 to 42ca441 Compare March 18, 2026 16:01
…xplorer onto a diagram

Bug: #2056
Signed-off-by: Pierre-Charles David <pierre-charles.david@obeo.fr>
@pcdavid pcdavid force-pushed the pcd/fix/message-on-drop-visible-element branch from 42ca441 to b585446 Compare March 18, 2026 16:20
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.

Dropping an Element which is already visible in a Package node does not give any feedback

1 participant