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 dispatching an action in the host extension (e.g. SaveModel, ExportSvg etc.) adopters currently have to manually define
whether the action should be sent to the client, the server or both.
However, both client and server already provide information about their handled actions so we could grab this information in the WebviewEndpoint and introduce automatic dispatching to the correct handling target (client/server) for actions issued by the host extension.
The text was updated successfully, but these errors were encountered:
…t extension
Introduce `dispatchAction` method in `GLSPVSCodeConnector`.
This method uses the handled action kinds provided by server/client to determine wether the action should be forwarded to client and/or server.
Deprecate `sendActionToActiveClient` and `sendActionToClient` methods (and use `dispatchAction` internally).
Fixeseclipse-glsp/glsp#1259
…t extension
Introduce `dispatchAction` method in `GLSPVSCodeConnector`.
This method uses the handled action kinds provided by server/client to determine wether the action should be forwarded to client and/or server.
Deprecate `sendActionToActiveClient` and `sendActionToClient` methods (and use `dispatchAction` internally).
Fixeseclipse-glsp/glsp#1259
When dispatching an action in the host extension (e.g. SaveModel, ExportSvg etc.) adopters currently have to manually define
whether the action should be sent to the client, the server or both.
However, both client and server already provide information about their handled actions so we could grab this information in the
WebviewEndpoint
and introduce automatic dispatching to the correct handling target (client/server) for actions issued by the host extension.The text was updated successfully, but these errors were encountered: