Repository navigation
docs: fix commas in image generation workflow examples - #167
Merged
Merged
Conversation
davidhu2000
approved these changes
Sep 8, 2026
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.
The synchronous and asynchronous Headshot Generator and Photo Colorizer examples omit the comma before
wait_for_completion, so copying them raises a Python syntax error. Add the four missing commas in the custom documentation sections.These README examples are also consumed by web-app code-sample generation and the published API reference. The docs acquisition audit in magichourhq/docs#499 corrects the current reference snapshot; after this source fix is merged, run the existing code-sample sync and publish the refreshed OpenAPI data so subsequent docs syncs retain it. The generator already adds the required separator; no generator or runtime changes are needed.
Validation: all 174 Python fenced snippets across SDK READMEs parse with
ast.parse;git diff --checkpasses. This checks syntax only; no API generation or release was performed.