Releases: nocode-js/sequential-workflow-designer
0.10.2
0.10.1
0.10.0
Refactored the step component interface. Extracted the logic of the step validation to a separated layer called badges. This allowed to create a new type of badge: counter. The counter badge is available in the pro version.
Additionally, now it's possible manually refreshing the validation from outside of the designer. The validation is a special case of a badge. To refresh the validation you need to call the updateBadges method.
designer.updateBadges(); 0.9.2
0.9.1
0.9.0
Breaking Changes
This version changes the main configuration. The "isHidden" properties are prohibited. To hide the control bar or other UI component you need to set false in the corresponding configuration property.
const configuration = {
toolbox: false,
editors: false,
controlBar: false,
// ...
};To display components you need to set a proper value.
const configuration = {
toolbox: {
groups: [ /* ... */ ]
},
editors: {
globalEditorProvider: () => { /* ... */ },
stepEditorProvider: () => { /* ... */ },
},
controlBar: true,
// ...
};0.8.1
0.8.0
- This release introduces a better support for TypeScript.
- The model of the workflow definition is moved from the
sequential-workflow-designerpackage to thesequential-workflow-modelpackage. By this it's possible to create a common package with your workflow model and use it for the front-end and back-end applications at the same time. Thesequential-workflow-designerpackage exports definition types as before, but these types come from thesequential-workflow-modelpackage. You don't have to include thesequential-workflow-modelpackage to your project if you don't need it. You can read more about this approach here.
Breaking Changes
TaskStep, SwitchStep, ContainerStep interfaces are depreciated now. Those types will be removed in the future.
🤩 We launched a new project: Sequential Workflow Machine. It's a JavaScript workflow engine for the frontend and the backend. The engine uses exactly the same data model as the Sequential Workflow Designer. It means you can use the same workflow definition for the designer and the engine. The new package is powered by the xstate library.
0.7.0
- The step validator has two parameters from now:
stepandparentSequence. - Added new editing restrictions:
isDraggableandisDeletable.
Breaking Changes
- Refactored step components by introducing the
StepContextinterface. - Renamed
.sqd-step-start-stop*CSS selectors to.sqd-root-start-stop*.