fix: Handle missing Power Puter workflow metadata in API requests - #751
Open
mvanhorn wants to merge 1 commit into
Open
fix: Handle missing Power Puter workflow metadata in API requests#751mvanhorn wants to merge 1 commit into
mvanhorn wants to merge 1 commit into
Conversation
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.
Normalize the workflow passed to
_Puterat the existingRgthreePowerPuter.mainboundary: use the suppliedextra_pnginfo.workflowwhen present and fall back to an empty{"nodes": []}workflow when the metadata or workflow key is absent. Power Puter currently tests membership in the hiddenextra_pnginfovalue before checking whether that value exists.Queue a Power Puter prompt through the API without
extra_pnginfo/workflow metadata and verify a string-manipulation expression completes with the expected output instead of raisingTypeError; Queue the same node through the normal UI workflow path with workflow metadata and verify its existing expression output remains unchanged.Fixes #726