@eclipse-glsp-examples/workflow-server-bundled
Advanced tools
Changelog
GLSElkLayoutEngine
that skipped layouting of certain edges #23 - Contributed on behalf of STMicroelectronicsshutdown
was called #33 - Contributed on behalf of STMicroelectronicsPromise
s and MaybePromise
s have proper rejection handling #36- Contributed on behalf of STMicroelectronicsRequestModelActionHandler
#54AbstractJsonModelStorage
to ensure that Windows file paths are properly converted #55fs-extra
#56EdgeCreationChecker
API. Adopters can implement this to handle dynamic edge creation validation requests. #60GForeignObjectElement
+ builder class #61EdgePlacement
-> GEdgePlacement
(affected classes: GEdgeLayoutable
, GLabel
)GLayoutContainer
-> GLayouting
(affected classes: GCompartment
, GGraph
, GNode
)GShapePreRenderedElement
-> GShapedPreRenderedElement
@eclipse-glsp/server-node
package to provide entry points for both node and browser-only environments #37
@eclipse-glsp/server
. This change affects all import namespaces.@eclipse-glsp/server/node
@eclipse-glsp/server/browser
OperationHandler
has been refactored from an interface to a common abstract base class. The execute
method now has to return a MaybePromise<Command|undefined>
CreateOperationHandler
to an interface instead of a classGModel
prefixModelState
interface no longer has an isDirty
flag. Dirty state is now handled by the CommandStack
GLSPServer
and GLSPServerLauncher
API #44 - Contributed on behalf of STMicroelectronics
@eclipse-glsp/protocol
GLSPServer
implementation is no longer relies on json-rpc implementation details.JsonRpcGLSPServerLauncher
CommandStack
API to support undo/redo of model changes #38 #39 - Contributed on behalf of STMicroelectronics
ModelState
no longer has a isDirty
propertyOperationHandler
API@postConstruct
) with asynchronous results are no longer supportedModelSubmissionHandler
to enable handling of RequestModelAction
as proper request action
submitInitialModel
method that is called by the RequestModelActionHandler
configureClientActions
from DiagramModule
as client actions are now implicitly configured via InitializeClientSession
requestClientActionHandler
and replace with ClientActionForwarder
ServerStatusAction
-> StatusAction
and ServerMessageAction
-> MessageAction