Repository navigation
feat(content): generate REST and GraphQL client examples - #29
Merged
Merged
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
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.
Owner-created Content snapshots can now generate client examples through Use this API. Published REST and typed GraphQL calls expose the same eight language targets as ordinary APIs, with an explicit saved-draft choice. The examples require a separate owner-issued query runtime key pinned to the current publication.
Metadata and generation recheck the original owner proof inside the transaction and validate the sealed source. Generation returns text without executing the API, issuing keys, or persisting example input. The dashboard keeps unsupported snapshot editing and publication actions guarded.
Validation:
This is a source delivery for 0.29.0-alpha.0. It does not publish a new executable or claim that generated examples were compiled in every target language. Live Content reads remain the next separate milestone.
Exact reviewed head:
04e443efcac700a94d2e37aa412da85d373afab4. CI passed all three serialized jobs: 423 backend tests / 10,235 assertions, 84 browser tests, and 11 portable tests / 1,307 assertions.