tasklist not opening editor (no binding for EditorContextService) #1527
-
Hoping someone can help or at least point me in the right direction!.. I'm trying to get the gslp-example node-json-theia running in my theia project
I have basically copied the following glsp-example folders into my project repo (and set/edited package.json etc.)
Everything builds ok and Theia runs ok. The glsp log looks ok: 6:09:38 PM info - [SocketServerLauncher] The GLSP server is ready to accept new client requests on port: 36523
6:09:56 PM info - [SocketServerLauncher] Starting GLSP server connection
6:09:56 PM info - [DefaultGLSPServer] Initializing server with: applicationId: 45f14fbc-3e71-400c-b62b-00dd8bb48c80, protocolVersion: 1.0.0 However, when I click on the Uncaught (in promise) Error: No matching bindings found for serviceIdentifier: EditorContextService
at _validateActiveBindingCount (planner.ts:170:15)
at _getActiveBindings (planner.ts:108:3)
at _createSubRequests (planner.ts:205:22)
at plan (planner.ts:339:5)
at container.ts:1084:45
at Container._get (container.ts:1006:37)
at Container._getButThrowIfAsync (container.ts:1010:60)
at Container.get (container.ts:399:17)
at GLSPDiagramWidget.configure (glsp-diagram-widget.ts:112:82)
at Object.create (diagram-widget-factory.ts:47:27) I'm going round in circles!.. any help or ideas appreciated. PS. The glsp-example tasklist runs ok on my machine out the box (i.e. from a new clone repo) |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 2 replies
-
So, trawling through the startup console log, I found the following warning: 2025-05-27T13:33:52.844Z root WARN Couldn't restore widget for tasklist-diagram-diagram-manager. Error: Error: No matching bindings found for serviceIdentifier: EditorContextService Is the "double tasklist" an issue in |
Beta Was this translation helpful? Give feedback.
-
Hi @metadatadriven, export function deriveDiagramManagerId(diagramType: string): string {
return diagramType + '-diagram-manager';
} In your case everything is building correctly, but then during runtime you get an inversify error. Please check if that is the case. (You can use
|
Beta Was this translation helpful? Give feedback.
-
Thanks for your suggestion @tortmayr - I did have a "hello-world" extension in the project that had inversify as a dependency in the extension package.json - I have removed the extension from the project completely, also added a yarn resolution for inverify to 6.1.3. I have deleted node_modules and yarn.lock and re-installed and re-built everything. Unfortunately I am still getting the same runtime error. My $ yarn why inversify
yarn why v1.22.22
[1/4] Why do we have the module "inversify"...?
[2/4] Initialising dependency graph...
[3/4] Finding dependency...
[4/4] Calculating file sizes...
=> Found "[email protected]"
info Reasons this module exists
- "_project_#browser-app#@theia#core" depends on it
- Hoisted from "_project_#browser-app#@theia#core#inversify"
- Hoisted from "_project_#tasklist-glsp-client#@eclipse-glsp#client#@eclipse-glsp#sprotty#sprotty#inversify"
info Disk size without dependencies: "2.25MB"
info Disk size with unique dependencies: "4.06MB"
info Disk size with transitive dependencies: "4.23MB"
info Number of shared dependencies: 2
Done in 0.74s. I'm assuming that the |
Beta Was this translation helpful? Give feedback.
-
The
Did you also upgrade the other GLSP dependencies to 2.4.0? |
Beta Was this translation helpful? Give feedback.
The
EditorContextService
is a core service that is bound in the default module of GLSP. If inversify cannot resolve it, that's typically an indicator that something is wrong with the overall setup.Did you also upgrade the other GLSP dependencies to 2.4.0?
(@eclipse-glsp/client and @eclipse-glsp/server)