eclipse-emfcloud/coffee-editor

After emfcloud related updates, command operations are failing on coffee tree editor(superbrewer3000.coffee)

mishaltripathi opened this issue · 5 comments

Hi,

After latest commit/updates of emfcloud on coffee editor, I am not able to perform any operation(add/set/delete) on coffee tree editor (superbrewer3000.coffee) and getting below error in my console.

error_log1
error_log2

While it was working before the latest updates. Please have a look into it.

Thanks,
Mishal

Hi @mishaltripathi ,

thank you for your report. We did not encounter this error yet.
Did you try running git clean -dxf and then reinstalling and rebuilding everything again? Maybe you have a weird state in your node_modules?
Please let us know.

Best,
Eugen

Thanks @eneufeld for your response. I tried your suggestion but didn't help. I also debugged it and found that payload doesn't contain required data to create command at decoding part of DefaultJsonCodec(backend) where its expected to load json resource from payload and return command object.

Hi @mishaltripathi ,
I tried again and build from root. I can reproduce your error now.
I'm currently updating the whole edit functionality to use json patches. So I would suggest to focus on this update as it will give us more features.

Hi,
I encountered the same problem in the last days. I tried older versions but always got a "deal breaking" bugs

Editing works partially with commits 4ebc695 , 8456e17 (After updating dependencies of xtext.sdk.feature.group for build) where I could change the properties of the machine. But most properties for example of the ControlUnit don't persist when going to another element.

Hi, I encountered the same problem in the last days. I tried older versions but always got a "deal breaking" bugs

Editing works partially with commits 4ebc695 , 8456e17 (After updating dependencies of xtext.sdk.feature.group for build) where I could change the properties of the machine. But most properties for example of the ControlUnit don't persist when going to another element.

i believe this comment was also posted as part of an ongoing discussion in Discourse, so I am closing this issue. Feel free to reopen if you disagree,