Repository navigation
feat(copy): correct SDK download workflow examples - #576
Merged
Merged
Conversation
runshouse
changed the title
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
2 participants
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.
Fix SDK download examples in the existing inputs/outputs guide: Node workflow options belong in the second argument; automatic examples explicitly use Free-compatible
z-image-turboat640px, check terminal status and nonempty saved paths before claiming success, and retain the original project ID for recovery. Manual multi-output examples fetch an explicit image-project status, use defined variables and print success only when their download helper returns true. Explain actualexpires_at, cached URL reuse and Python streaming versus Node whole-file buffering. SDK/API, retention and signing behavior are unchanged.Verified against published
magic-hour@0.83.0, current Node/Python helper contracts and canonical Free model/resolution access. Independent review and remote Mintlify broken links, canonical Prettier and whitespace checks passed. No production generation/download or payment performed; this does not fix SDK exceptions before a result is returned or universal partial-download recovery. All three native checks passed at HEAD3b0b17b7da968388e6edb0b506e65e5151d8b86a; Mintlify deployment skipped. No SDK runtime or tests changed.