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
{{ message }}
Repository navigation
Take API field descriptions in output schemas from @sentry/api #1853
Output schemas that document API fields still add descriptions by hand: the CLI wraps generated @sentry/api/valibot fields in pipe(field, description("…")) because the generated schemas carry no description() actions. Examples: SentryFeedbackSchema (src/types/feedback.ts), IssueEventSchema (src/types/sentry.ts), the replay list output schema (src/types/replay.ts), and issue tags (src/commands/issue/tags.ts). Those descriptions drive --help field tables and the skill references, and can drift from the API spec.
Depends on @sentry/api emitting descriptions in its generated valibot schemas.
Activity
linear-code commentedon Nov 3, 2026
MCP-1150
feat(apidocs): Describe TypedDict response fields with ApiDescription (…
feat(validators): Attach OpenAPI descriptions to Valibot and Zod sche…
feat(apidocs): Describe team, role and user response fields (#129993)
ref(cli): Take API field descriptions from @sentry/api (getsentry#1967)