coffee-tree-editor-widget and theia NavigatableTreeEditorWidget incompatible #73
-
|
In building the coffee editor web piece from the command line, eslint fails on problems in coffee-tree-editor-widget, specifically because various properties are not assignable to the same properties in the base type NavigatableTreeEditorWidget (which is from @eclipse-emfcloud/theia-tree-editor). The properties are deleteNode, (node: Readonly) => void, addNode, ({ node, type, property }: AddCommandProperty) => void, handleFormUpdate, and (data: any, node: Node). I really need some help with this! This is code as delivered that I have not yet modified. TIA original thread by GaryKopp |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments
-
|
[Lucas Koehler] Hello, how did you build the coffee editor? |
Beta Was this translation helpful? Give feedback.
-
|
[GaryKopp] Thanks for the response, Lucas. I was building with yarn. And yes, I had deleted yarn.lock. After restoring yarn.lock web builds properly. I'm sorry to say I'm a novice with yarn. I thought yarn.lock would be rebuilt during a fresh build. My intention was to make sure node-modules didn't end up with modules that were no longer needed since I have deleted some TypeScript stuff from the application. It leaves me wondering how yarn.lock gets built initially or how it might be modified as the application evolves, but I'll understand if you don't want to explain this since it's really my responsibility to master yarn. |
Beta Was this translation helpful? Give feedback.
-
|
[Lucas Koehler] The yarn.lock is rebuilt with a fresh build. However if it was deleted before, it might draw in newer versions than intended (like in your case). It is also updated when you add new dependencies or tell yarn to update existing ones. More info on the yarn.lock can be found here: https://classic.yarnpkg.com/en/docs/yarn-lock/ |
Beta Was this translation helpful? Give feedback.
-
|
[GaryKopp] Thanks again. I'll study the yarn doc. |
Beta Was this translation helpful? Give feedback.
[Lucas Koehler]
The yarn.lock is rebuilt with a fresh build. However if it was deleted before, it might draw in newer versions than intended (like in your case). It is also updated when you add new dependencies or tell yarn to update existing ones. More info on the yarn.lock can be found here: https://classic.yarnpkg.com/en/docs/yarn-lock/