Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GLSP Marker display fails after reload #449

Closed
sgraband opened this issue Jun 1, 2022 · 1 comment · Fixed by #457
Closed

GLSP Marker display fails after reload #449

sgraband opened this issue Jun 1, 2022 · 1 comment · Fixed by #457
Assignees
Labels
bug Something isn't working

Comments

@sgraband
Copy link
Contributor

sgraband commented Jun 1, 2022

After reloading the application once, the GLSP editor no longer displays the error markers.

The validation is still correctly triggered and updated though, as the results can still be seen in the problems view.

Furthermore when clicking on the entry in the problems view you are no longer forwarded to the correct element in the diagram.

This is likely due to some ID stuff that is going wrong. Maybe the GLSP server assigns new IDs after reload hence the validation results can no longer be paired with a node.

@sgraband sgraband added the bug Something isn't working label Jun 1, 2022
@sgraband sgraband self-assigned this Jul 20, 2022
@sgraband
Copy link
Contributor Author

After some debugging the resource on the modelserver does not have an idToEObject Map after reloading. This then leads to the ID returned being -1. Which obviously cannot be mapped by the GLSP Server.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
1 participant