Skip to content

[2194] Properly report feedback messages while moving elements in GV#2217

Open
adaussy wants to merge 1 commit into
cooldownfrom
ada/enh/2194
Open

[2194] Properly report feedback messages while moving elements in GV#2217
adaussy wants to merge 1 commit into
cooldownfrom
ada/enh/2194

Conversation

@adaussy
Copy link
Copy Markdown
Contributor

@adaussy adaussy commented May 18, 2026

Bug: #2194

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.

Bug: #2194
Signed-off-by: Arthur Daussy <arthur.daussy@obeo.fr>
@adaussy adaussy marked this pull request as ready for review May 19, 2026 14:51
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it mandatory to create a new .sql file?
Please consider with the greatest attention the need of such file, may be there are existing ones that could suit your needs.
Every new .sql is a step into a more complex integration tests suite to maintain.


private final DiagramQueryElementService diagramQueryElementService;

private final IFeedbackMessageService feedbackMessageService;
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would prefer you add the two SW services in first positions, here, in the constructor parameters and constructor body.

}

private String getLabel(Object droppedElement) {
StyledString styledLabel = this.labelService.getStyledLabel(droppedElement);
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it really necessary to invoke getStyledLabel here?

private String getLabel(Object droppedElement) {
StyledString styledLabel = this.labelService.getStyledLabel(droppedElement);
if ((styledLabel == null || styledLabel.toString().isEmpty()) && droppedElement instanceof EObject droppedEObject) {
styledLabel = StyledString.of(droppedEObject.eClass().getName());
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No need to String => StyledString => String.
You should probably create a String variable as the first line of this method body, then affect droppedEObject.eClass().getName() to it.

private String getLabel(Object droppedElement) {
StyledString styledLabel = this.labelService.getStyledLabel(droppedElement);
if ((styledLabel == null || styledLabel.toString().isEmpty()) && droppedElement instanceof EObject droppedEObject) {
styledLabel = StyledString.of(droppedEObject.eClass().getName());
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No need to String => StyledString => String.
You should probably create a String variable as the first line of this method body, then affect droppedEObject.eClass().getName() to it.

}

private String getLabel(Object droppedElement) {
StyledString styledLabel = this.labelService.getStyledLabel(droppedElement);
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it really necessary to invoke getStyledLabel here?

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.

ISysMLMoveElementService#moveSemanticElement user feedback in diagram tools context

2 participants