v7.0.1

7.0.1 (2024-03-31)

v7.0.0

7.0.0 (2024-03-31)

Bug Fixes

• output: don't allow empty outputs (25dc301)

BREAKING CHANGES

• output: Any empty outputs will now fail type check. Any endpoints MUST now have at least
  one key in the output object

v6.3.0

6.3.0 (2024-03-30)

Features

• Add error handlers (#23) (ef423c8)

v6.2.0

6.2.0 (2024-03-30)

• fix: narrow response types

makes response types not arbitrary. Users can no longer pass whatever status with whatever bodies

• feat(openapi): support zod openapi extension

• docs(openapi): improve docs

• feat(createapi): add support for nested routes

Allows specifying one level of nesting when defining the routing object

• docs(readme): nested routing example

Add an example of how to use nested/prefixed routes

• fix(createendpoint): require at least one handler

No longer allow an empty array to be passed to the handler parameter

• test(integration): add integration tests for documentation and input validation

v6.1.0

6.1.0 (2024-03-30)

Features

• createendpoint: allow to omit the input property (#16) (d2851b0)

v6.0.0

6.0.0 (2024-03-30)

Bug Fixes

• update dependencies (#15) (38eb09f)

BREAKING CHANGES

• this version fixes the open api spec version to 3.1.0 and does not allow the user
  to change it

• ci: update node versions

• fix(test): fix test script

• ci: remove node 16

v5.0.2

5.0.2 (2022-09-25)

Bug Fixes

• force release (464cf15)

v5.0.1

5.0.1 (2022-08-18)

v5.0.0

5.0.0 (2022-08-18)

• feat!: type safety for reseponse status and body (51ef0a0)

BREAKING CHANGES

• types will now require that you use the correct body for a given status when calling res.json

v4.0.0

4.0.0 (2022-02-06)

Features

• add support for transforms (2a3989a)
• automatic error recovery (bcb3ea3)
• cleaner error message (b780945)

BREAKING CHANGES

• Remove outputHeaders from the createEndpoint params object. The output
  property now requires you to specify, for each status code, an object which must have a body
  property, containing the Zod schema for the body of the response for that status. Optionally, you
  can also specify a headers property to each status code containing the response headers for that
  status code