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
When composer.json is in invalid json, you modify to be valid again in the json editor and while saving change page to say overview page. Json state is valid, and thus page is enabled again but new contents are no parsed into it.
Who comes first, saving that also sets the valid state again to true and the page change which actually should parse the new contents, however doesn't already know about the valid state change and thus does nothing. Saving finishes later and enables the page which you are on already but still has the old contents.
Reproduce:
make sure you have something written into description
go to json editor, modify description which turns composer.json invalid
save
check pages they are disabled, invalid message is up in the header
check also overview page it still has the old value of description when it was valid
write something new into description, modify to make it valid again
hover the configuration page with the mouse
simultaneously hit cmd/ctrl+s to save and click on the overview page
overview page doesn't contain the new description value, however composer.json is valid again and saved
check back json editor, old description value
The text was updated successfully, but these errors were encountered:
When composer.json is in invalid json, you modify to be valid again in the json editor and while saving change page to say overview page. Json state is valid, and thus page is enabled again but new contents are no parsed into it.
Who comes first, saving that also sets the valid state again to true and the page change which actually should parse the new contents, however doesn't already know about the valid state change and thus does nothing. Saving finishes later and enables the page which you are on already but still has the old contents.
Reproduce:
The text was updated successfully, but these errors were encountered: