FlowDrop 1.7.0: Workflow-Level Settings Schema
FlowDrop 1.7.0 lets integrators inject custom fields into the Workflow Settings panel via a typed schema, with values persisted alongside the workflow.
FlowDrop 1.7.0 is a focused release: one new prop, a clean set of fixes, and a small internal refactor that makes the intent of the port compatibility guard explicit.
Workflow settings schema
Pass a ConfigSchema to the App component via the new workflowSettingsSchema prop and those fields appear in the Workflow Settings panel alongside the built-in name and description fields. Values are stored in a new workflow.config object and round-trip correctly through load and save — the host’s backend receives them with the rest of the workflow document.
This is the right place for workflow-level metadata that belongs to the workflow author rather than the end user: environment tags, execution tier, retry policy, or any other fields your platform needs attached to a workflow definition.
Reserved names (name, description, format) are filtered out with a warning — collisions with built-in fields would silently break the settings panel, so this is enforced at mount time.
Fixes
CodeEditor JSON string preservation — external value updates to a CodeEditor field were stripping quotes from JSON string values. The field now preserves them correctly when a new value arrives from outside.
Port compatibility preservation on mount — App was reinitialising the port compatibility checker on every mount, discarding any custom port config the consumer had already set. It now skips reinitialisation if a checker is already in place.
SimpleNode description placeholder — nodes without a description were rendering a default "A configurable simple node" paragraph. That text is gone; nodes with no description render nothing.
Upgrading
npm install @flowdrop/flowdrop@1.7.0No breaking changes.