sequential-workflow-designer
Advanced tools
Changelog
0.13.2
The react package supports two types of editor providers. Now it's possible to use a provider that returns native DOM elements. We don't want to depreciate the previous approach, this change increases flexibility of the react package.
// 1. custom react component
<SequentialWorkflowDesigner stepEditor={<StepEditor />} ... />
// 2. native editor provider
function stepEditorProvider(step) {
const editor = document.createElement('div'); /* ... */
return editor;
}
<SequentialWorkflowDesigner stepEditor={stepEditorProvider}> ... />
Changelog
0.13.1
The canMoveStep
callback is not called when the step is moved to the same position.
🤩 We launched a new project: Sequential Workflow Editor. Don't write step editors manually, build them.
Changelog
0.13.0
The StepTraverser
is not a part of the designer package anymore. This class is moved into the model package and it's called DefinitionWalker
now. The responsibility of determining children of a step is not part of the StepExtension
interface anymore.
Changelog
0.12.0
The designer has allowed only the validation of the steps so far. The root of the definition could be edited by the global editor, but the validation was not possible. This version adds a new type of the validator: the root validator. The new validator affects on the result of the definition validation (designer.isValid()
).
validator
property in the steps
group of the configuration is deleted. Use the step
property in the validator
group instead.definition
.const configuration = {
steps: {
validator: /* DEPRECIATED */,
},
validator: {
step: (step, parentSequence, definition) => { /* ... */ },
root: (definition) => { /* ... */ }
},
// ...
};
Changelog
0.11.0
customActionHandler
handler:
type
property from the object.step
parameter is nullable now,context
parameter that allows to notify about changes in the definition.sqd-label-primary
and sqd-label-secondary
.Changelog
0.10.2
Changelog
0.10.1
Changelog
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();