-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Bump API schema to c23d6d90 #14992
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
Open
getsantry
wants to merge
1
commit into
master
Choose a base branch
from
bot/bump-api-schema-to-c23d6d90
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Bump API schema to c23d6d90 #14992
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
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.
Potential bug: The
resolveOpenAPI
function doesn't handle non-200 HTTP responses fromfetch
before callingresponse.json()
, which can cause a crash if the external API returns an error.Description: The
resolveOpenAPI
function fetches an OpenAPI schema from a raw GitHub URL. It directly callsresponse.json()
on the result without first checking if the HTTP request was successful (e.g., viaresponse.ok
). If the fetch fails for any reason, such as a 404 error or a temporary GitHub outage, the response will likely be an HTML error page. Attempting to parse this HTML as JSON will throw aSyntaxError
, causing an unhandled exception. This will crash the documentation build process and also cause server-side rendering failures for API documentation pages, as the function is used in both critical paths.Suggested fix: Before calling
await response.json()
, add a check for the response status. If!response.ok
, throw an informative error to prevent the application from crashing due to an attempt to parse a non-JSON response. For example:if (!response.ok) { throw new Error(
Failed to fetch OpenAPI schema: ${response.statusText}); }
.severity: 0.7, confidence: 0.95
Did we get this right? 👍 / 👎 to inform future reviews.