-
Notifications
You must be signed in to change notification settings - Fork 5
feat: adding sdk examples to api reference and enabling the playground #313
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
pengying
merged 1 commit into
main
from
03-31-feat_adding_sdk_examples_to_api_reference_and_enabling_the_playground
Apr 1, 2026
+50
−7
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,26 @@ | ||
| name: Check docs config | ||
|
|
||
| on: | ||
| pull_request: | ||
| paths: | ||
| - 'mintlify/docs.json' | ||
|
|
||
| jobs: | ||
| check-openapi-reference: | ||
| runs-on: ubuntu-latest | ||
| steps: | ||
| - uses: actions/checkout@v4 | ||
|
|
||
| - name: Ensure docs.json uses production OpenAPI URL | ||
| run: | | ||
| EXPECTED_URL="https://app.stainless.com/api/spec/documented/grid/openapi.documented.yml" | ||
| if grep -q '"openapi.yaml"' mintlify/docs.json; then | ||
| echo "::error file=mintlify/docs.json::docs.json references local 'openapi.yaml' instead of the production Stainless URL." | ||
| echo "" | ||
| echo "The openapi field must point to:" | ||
| echo " $EXPECTED_URL" | ||
| echo "" | ||
| echo "Local openapi.yaml is only for development (make mint handles this automatically)." | ||
| exit 1 | ||
| fi | ||
| echo "docs.json openapi reference looks good." |
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"api"blockThe new
"api"block uses 1-space indentation for the top-level key and 3-space indentation for its children, while the rest ofdocs.jsonuses a consistent 2-space indentation (e.g.,"logo","navbar","integrations"at line 288+). The closing},is at 2 spaces which is correct, but the opening key and nested keys are misaligned.Prompt To Fix With AI
Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!