You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The API endpoint to get dependabot alerts for an org/enterprise do not contain the page parameter.
When calling these endpoints, the returned links for rel=next etc. include the page parameter. Using the page parameter in subsequent requests works like expected, therefore the schema seems to be inconsistent with the implementation here.
Other Organizational Alert Endpoints (Secret Scanning etc.) have the page parameter specified in the schema.
Expected
The schema should include the page parameter for the endpoint.
Reproduction Steps
Call Endpoint
Response data returns links with the page set in the links section.
As I am using an lib that is auto generated from the schemas this creates issues as it tries to use a value for page on an object that does not know 'page'.
Thanks :)
The text was updated successfully, but these errors were encountered:
👋 Thanks for the feedback. I've reached out to the team that handles this API to confirm this is the right change, and we'll follow up if there are any additional questions.
BenedictStrunk-otto
changed the title
/orgs/{org}/dependabot/alerts schema is missing 'page'
[Schema Inaccuracy] /orgs/{org}/dependabot/alerts schema is missing 'page'
Dec 4, 2024
Schema Inaccuracy
The API endpoint to get dependabot alerts for an org/enterprise do not contain the page parameter.
When calling these endpoints, the returned links for rel=next etc. include the page parameter. Using the page parameter in subsequent requests works like expected, therefore the schema seems to be inconsistent with the implementation here.
https://docs.github.com/en/rest/dependabot/alerts?apiVersion=2022-11-28#list-dependabot-alerts-for-an-organization
Other Organizational Alert Endpoints (Secret Scanning etc.) have the page parameter specified in the schema.
Expected
The schema should include the page parameter for the endpoint.
Reproduction Steps
As I am using an lib that is auto generated from the schemas this creates issues as it tries to use a value for page on an object that does not know 'page'.
Thanks :)
The text was updated successfully, but these errors were encountered: