Replies: 2 comments 2 replies
-
If you see that the dirty flag has changed on the client size this usually only indicates that the GLSP client Model has changed. This does not necessarily mean that your server model was updated too. At least this was a topic which took me a long time to understand in my own project. It is necessary that on each change operation you update your source model. But my assumption here is that your source model and your glsp model are not the same. If this is the case in your project than you can ignore my answer as I am not the expert here ;-) |
Beta Was this translation helpful? Give feedback.
-
Hi @Adem-Kri,
How do you propagate this changes to the glsp server? The diry state is only updated automatically if you send (& handle) an Operation to the server. Plain actions typically should not modifiy the source model. If you can't (or don't want to) send an operation, then you should send a |
Beta Was this translation helpful? Give feedback.
-
Hello,
I am currently working on a graph that has a properties panel which displays information about the selected element. This panel also allows me to make changes to the element's properties.
However, I have noticed that when I hit save, the changes I made are not saved unless I move something in the graph. After some research, I found that setting the dirty state can help solve this issue.
Could you please explain how to implement the dirty state in my project?
Thank you.
Beta Was this translation helpful? Give feedback.
All reactions