Repository navigation
Hide deprecated 504 responses from schema - #487
Conversation
|
Schema Diff vs Published Schemas
No schema changes detected between local build output and published GitHub Pages schemas. |
There was a problem hiding this comment.
Copilot review overview
🟡 Changes recommended
Pipeline-level tests are needed to protect the documented SDK compatibility guarantee.
Review effort: Balanced
Findings: 1
What changed in this PR
Hides deprecated 504 responses from documentation while preserving SDK compatibility.
Changes:
- Adds a transformer for deprecated responses.
- Marks two event
504responses as deprecated. - Removes internal markers from SDK schemas and adds changesets/tests.
| File | Description |
|---|---|
utils/transformers/transformSchema.ts |
Configures documentation and SDK pipelines. |
utils/transformers/removeDeprecatedResponsesTransformer.ts |
Implements deprecated-response removal. |
utils/transformers/removeDeprecatedResponsesTransformer.spec.ts |
Adds unit coverage. |
schemas/paths/events.yaml |
Marks Events Search 504 as deprecated. |
schemas/paths/event.yaml |
Marks Get Event 504 as deprecated. |
.changeset/deprecated-response-504-events.md |
Documents Get Event behavior. |
.changeset/deprecated-response-504-events-search.md |
Documents Events Search behavior. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
mcnulty-fp
left a comment
There was a problem hiding this comment.
Thanks for working on this! A few changes to make. Let me know if I can clarify my comments.
891e99d to
715cd0a
Compare
mcnulty-fp
left a comment
There was a problem hiding this comment.
Looks good! Just one nit
Co-authored-by: Dan McNulty <212590662+mcnulty-fp@users.noreply.github.com>
pnpm run changesetto create a changeset. |

No description provided.