You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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.
The text was updated successfully, but these errors were encountered: