fix: preserve workflow node/edge keys from case conversion#60
Merged
PennyroyalTea merged 1 commit intomainfrom Feb 26, 2026
Merged
fix: preserve workflow node/edge keys from case conversion#60PennyroyalTea merged 1 commit intomainfrom
PennyroyalTea merged 1 commit intomainfrom
Conversation
…#57) Workflow nodes and edges keys (e.g. start_node, edge_start_to_agent) are user-defined identifiers, not schema fields. toCamelCaseKeys was converting them (start_node -> startNode), causing the API to reject pushes with "Workflow must contain a start node". Extract preserved-key checks into a shared PRESERVE_CHILD_KEYS set and add nodes/edges alongside the existing request_headers and dynamic_variables entries. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
nodesandedgeschild keys (e.g.start_node,edge_start_to_agent) are user-defined identifiers, not schema fields.toCamelCaseKeyswas converting them (start_node->startNode), causing the API to reject pushes with "Workflow must contain a start node"PRESERVE_CHILD_KEYSset, addingnodes/edgesalongside the existingrequest_headersanddynamic_variablesentriesedge_order,agent_id) are still correctly camel-casedFixes #57
Test plan
pnpm buildcompilespnpm test-- all 164 tests pass (3 new workflow key preservation tests, 5 existing tests updated to assert correct behavior)elevenlabs agents pullthenelevenlabs agents pushfor an agent without an explicit workflow🤖 Generated with Claude Code