When defining response schemas with status codes, only numeric HTTP status codes (like 200, 404, etc.) should be processed. Previously, the validator would crash if non-numeric keys were present in the response schema definition.

Error

undefined is not an object (evaluating 'maybeNameOrSchema.type')

This change adds a validation check to safely ignore any non-numeric status codes, making the schema validator more robust against invalid inputs.

And one of the use case is that we can set a default status in response schema as allowed by OpenAPI 3.0.4 specification.

const app = new Elysia().get(
  '/health',
  () => {
    return {
      status: 200,
      response: 'Hello world',
    };
  },
  {
    response: {
      200: t.String(),
      default: t.String(),
    },
  },
);

This will be generate in Swagger UI like this:

Also, fixes #1164