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.

Sign up for GitHub

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

Jump to bottom

Add possibility to persist Source Model through an API (e.g., from GLSP diagram side) #33

Open
hpopov opened this issue Sep 21, 2023 · 0 comments
Open

Add possibility to persist Source Model through an API (e.g., from GLSP diagram side) #33

hpopov opened this issue Sep 21, 2023 · 0 comments
Assignees
@hpopov
Labels
question Further information is requested

Comments

@hpopov
Copy link
Contributor

hpopov commented Sep 21, 2023

So that it is possible to edit the model solely from GLSP side (LMS Clients side)
@hpopov hpopov self-assigned this Sep 21, 2023
@hpopov hpopov added the question Further information is requested label Sep 21, 2023
hpopov added a commit that referenced this issue Sep 21, 2023
@hpopov
#33 Playing with PUT /persist API
fb8d663
hpopov added a commit that referenced this issue Sep 21, 2023
@hpopov
Revert "#33 Playing with PUT /persist API"
bd9a02b 
This reverts commit fb8d663.
hpopov added a commit that referenced this issue Sep 21, 2023
@hpopov
#33 Make persist endpoint work using custom LSP server request
fbd73b8
hpopov added a commit that referenced this issue Sep 21, 2023
@hpopov
#33 Hotfix the endless loop of save actions between LMS and GLSP
1e44d05 
By adding dirty state to LMSDocument. Need to fix this perhaps by differentiate SaveActions on GLSP side triggered programmatically (i.e., by LMS itself) and by the user (from GLSP client)
hpopov added a commit that referenced this issue Sep 21, 2023
@hpopov
#33 Fix issue with internal persistance of model
5acb34f
hpopov added a commit that referenced this issue Sep 26, 2023
@hpopov
#33 Hotfix the endless loop of save actions between LMS and GLSP
cd9717f 
By adding dirty state to LMSDocument. Need to fix this perhaps by differentiate SaveActions on GLSP side triggered programmatically (i.e., by LMS itself) and by the user (from GLSP client)
@hpopov hpopov mentioned this issue Oct 19, 2023
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@hpopov hpopov

Labels
question Further information is requested
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@hpopov