Skip to content

fix: incident schema validation prevents API startup#2172

Open
Wachhund wants to merge 1 commit into
TheMorpheus407:masterfrom
Wachhund:fix/incident-schema-validation
Open

fix: incident schema validation prevents API startup#2172
Wachhund wants to merge 1 commit into
TheMorpheus407:masterfrom
Wachhund:fix/incident-schema-validation

Conversation

@Wachhund

@Wachhund Wachhund commented Apr 14, 2026

Copy link
Copy Markdown

Summary

Fixes API startup crash: Failed building the validation schema for GET: /api/v1/game/sessions/:sessionId/incidents, due to error schema is invalid: data/required must be array

The incident route schemas used Zod types that produce invalid JSON Schema when Fastify processes them:

  • z.string().or(z.date()) → replaced with z.string() (dates arrive as ISO strings over HTTP)
  • z.union([z.literal(1), z.literal(2), z.literal(3), z.literal(4)]) → replaced with z.number().int().min(1).max(4)

One file changed, 5 lines.

Test plan

  • API starts without schema validation errors
  • GET /api/v1/game/sessions/:sessionId/incidents responds correctly
  • Incident severity validation still rejects values outside 1-4

…atibility

Fastify interprets route schemas as JSON Schema objects. The incident
schema used z.string().or(z.date()) and z.union([z.literal()]) which
produce invalid JSON Schema (data/required must be array), preventing
the API from starting. Replaced with simple z.string() and z.number()
since dates arrive as ISO strings over HTTP.
@Wachhund

Copy link
Copy Markdown
Author

Relates to #1747

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant