Releases: nocode-js/sequential-workflow-designer
0.5.3
0.5.2
This version introduces the first release of the Sequential Workflow Designer for React package.
0.5.1
0.5.0
- Fixed losing the disabled state during dragging.
- Fixed steps rendering with long labels.
- Added to the global editor and the step editor the common class:
sqd-editor.
Breaking Changes
- Changed a behavior of the default zoom. From now the designer shows a whole flow at the start.
- Zoom is aligned to the predefined constants.
0.4.0
This version brings rendering speed improvements. Check the stress-test.html example. This version contains many internal changes to support the folder component in the pro version.
Breaking Changes
- Replaced all icons to material icons.
- Normalized step CSS classes. All components have the
sqd-step-<componentType>-prefix from now.
0.3.0
This version introduces new build formats (ESM, UMD) of the package.
🤩 For more advanced use cases we prepared the paid pro package. The package is in the early stage. Currently it contains advanced components for steps. Here you can find more information and examples.
Breaking Changes
-
Default export of the
Designerclass is removed. Now you should import directly theDesignerclass.import { Designer } from 'sequential-workflow-designer'; Designer.create(/* ... */);
This affects CDN usage too.
<script src="https://cdn.jsdelivr.net/..."></script> <script> sequentialWorkflowDesigner.Designer.create(/* ... */); </script>
-
The package now contains two type of build: ESM and UMD. ESM build is located in the
libfolder. UMD build is located in thedistfolder. That means the URL to the CDN is also changed.<script src="https://cdn.jsdelivr.net/.../dist/index.umd.js"></script>
-
Static method
Designer.utils.nextId()is deleted. You should use thenext()from theUidclass. Example:import { Uid } from 'sequential-workflow-designer'; Uid.next();
-
Static method
Designer.utils.getParents()is deleted. You should use thegetStepParents()method from theDesignerclass. Example:designer.getStepParents(needleStep);
-
The
ComponentTypeis not an enum anymore. It's a type (string). This change doesn't affect serialized JSONs.
0.2.3
0.2.2
0.2.1
0.2.0
Editor's Context
We've changed an approach how the editors should notify the designer about changes in the definition. We've deleted revalidate() and notifiyDefinitionChanged() methods from the Designer class. Instead of this, now editors receive an editor's context.
interface StepEditorContext {
notifyNameChanged(): void;
notifyPropertiesChanged(): void;
}
interface GlobalEditorContext {
notifyPropertiesChanged(): void;
}
const config = {
// ...
editors: {
stepEditorProvider: (step: Step, context: StepEditorContext) => {
// ...
context.notifyPropertiesChanged();
// ...
},
globalEditorProvider: (definition: Definition, context: GlobalEditorContext) => {
// ...
context.notifyPropertiesChanged();
// ...
}
}
};Type Requirments
The type of a step cannot contain special characters from now. Check the type validator.
- ✅
someType - ✅
some-type - ✅
some_type - ❌
some type - ❌
someType!
By this, we could add the type to an element's class on the SVG canvas. That allows to customize components by CSS. Check this example.
Restrictions
We added canInsertStep, canMoveStep and canDeleteStep callbacks to the StepsConfiguration. You may restrict some activity in the designer by this.
const config = {
// ...
steps: {
canInsertStep: (step, targetSequence, targetIndex) => {
return targetSequence.length < 5;
},
canMoveStep: (sourceSequence, step, targetSequence, targetIndex) => {
return !step.properties['isLocked'];
},
canDeleteStep: (step, parentSequence) => {
return step.name !== 'x';
}
// ...
}
};