🐛 fix(open api resolver): Add Support for No Parameter API Documentation #11776
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.
some Sentry endpoints don't have any parameters, neither
pathnorquery. An example would beDocIntegrationsEndpointcurrently our Open API Resolver makes the assumption that there will always be parameters, so when trying to document parameter-less endpoints, we see the following error:
in this pr, i update the type of parameters to union with
undefinedto reflect that it might not exist and handle that case when building the api categories for documentation.API documentation without the parameter will now look something like:
