specification
specification copied to clipboard
serverlessworkflow
Serverless Workflow Specification
**What would you like to be added**: To allow for a way to name processed correlation keys. What I propose is to add a new `key` or `keyName` or whatever...
**What would you like to be added**: Rename the `eventDef`'s `correlation` object properties to have something shorter, as explicit, and cleaner IMHO. Currently, we have: ```yaml ... events: - name:...
**Many thanks for submitting your Pull Request :heart:!** **Please specify parts of this PR update:** - [x] Specification - [x] Schema - [ ] Examples - [ ] Extensions -...
**What would you like to be added**: Enforce naming conventions of most (if not all) components. I propose that we enforce using snake and/or kebab cased names. **Why is this...
**What would you like to be added**: To rename data filter properties **Why is this needed**: Having properties such as `stateDataFilter` when defining a state, or `actionDataFilter` when defining an...
As per spec "_The functions property can be either an in-line [function](https://github.com/serverlessworkflow/specification/blob/main/specification.md#Function-Definition) definition array, or an URI reference to a resource containing an array of [functions](https://github.com/serverlessworkflow/specification/blob/main/specification.md#Function-Definition) definition. Referenced resource can...
This allows implementors to impose restrictions on expression support for auth definition without affecting their compliance to the standard. **Many thanks for submitting your Pull Request :heart:!** **Please specify parts...
Updates to error handling * need to update examples and comparisons and go over spec doc.* * need to add sample that shows action error handling. rendered error handling section...
**What would you like to be added**: In Auth Definition section, explicitly mention that users, rather than hardcode the password string, can use $SECRET (afaik, $SECRET usage is restricted to...
What is a good approach for a while loop implementation using serverless workflow specs? Giving a simplified example, we have a list of book title in the state data and...
