Skip to content

fix: normalize workflow step parameters for CreateData/UpdateData#4

Open
chrisaddams wants to merge 2 commits intomainfrom
fix/workflow-trigger-and-data-pagination-public
Open

fix: normalize workflow step parameters for CreateData/UpdateData#4
chrisaddams wants to merge 2 commits intomainfrom
fix/workflow-trigger-and-data-pagination-public

Conversation

@chrisaddams
Copy link
Copy Markdown
Contributor

Summary

  • Normalizes user-friendly parameter names (entity/data) to platform format (entity_name/payload) for CreateData and UpdateData workflow actions
  • Uses JsonSerializer for payload string escaping instead of manual Replace calls, properly handling all Unicode control characters
  • Applies to both step-add and step-update commands

The platform expects entity_name (string) and payload (JSON string) for CreateData
and UpdateData actions, but users naturally pass entity (string) and data (object).
The CLI now auto-converts entity→entity_name and data→payload (serialized as JSON
string) when the action type is CreateData or UpdateData. ReadData/DeleteData only
get entity→entity_name normalization. Applies to both step-add and step-update.
Manual escaping missed Unicode control characters (U+0000-U+001F) that
JSON requires escaped. Let the framework handle it properly.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant