chore: Automated API v2 OpenAPI spec generation#17046
Conversation
Graphite Automations"Add foundation team as reviewer" took an action on this PR • (10/10/24)1 reviewer was added to this PR based on Keith Williams's automation. |
| @Post("/authorize") | ||
| @HttpCode(HttpStatus.OK) | ||
| @UseGuards(NextAuthGuard) | ||
| @DocsOperation({ |
There was a problem hiding this comment.
After talking to @ThyMinimalDev, we agreed to not add development-only docs.
There was a problem hiding this comment.
What was the reason for the decision? IMO the @DocsOperation docs are useful in the future for the team itself to understand how these endpoints are intended to be used.
There was a problem hiding this comment.
I think these are not useful for developers as they can simply check the input types, hiding these properties in prod was requiring more work than the actual benefits, we can always just have comments or tsdocs on the input types for dev endpoints
E2E results are ready! |
| @Post("/authorize") | ||
| @HttpCode(HttpStatus.OK) | ||
| @UseGuards(NextAuthGuard) | ||
| @DocsOperation({ |
There was a problem hiding this comment.
What was the reason for the decision? IMO the @DocsOperation docs are useful in the future for the team itself to understand how these endpoints are intended to be used.
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 2 Skipped Deployments
|
Pull request was converted to draft
|
This PR is being marked as stale due to inactivity. |
What does this PR do?
These should never be out of sync now.
Mandatory Tasks (DO NOT REMOVE)
How should this be tested?