• Added useValidatorOptions type for the user to define extra options
• Added the option includeAjvFormats to include extended ajv formats, also implemented by typebox 0.25+
• Added tests for body and query validator to test extended formats

The current behavior of throwing a 500 when extended schema option was just kept and added to the tests. We should evaluate error handling for this in the future. strictNullChecks was added to tsconfig to properly generate dynamic type checks in VSCode, as warned. As a .eslintrc was already existend, I also added the vscode configuration that implements auto format on save for this eslint config and the minimal possible options for the ts formatter to avoid conflicts.

Currently the error message is not helpful in certain cases (e.g. minLength validation).

Might also be worthwhile to change response to include not only the first error message.

Hey @kevinmarrec, great h3 addition, I had no problems with using it so far. As I am pretty new to TypeBox, I wanted to ask, what the best way would be to make sure that only the provided fields are actually on the request? From a security perspective, it is discussable, but sometimes you want to have paramA, paramB and paramC as query parameter and used validateQuery to define them as string (what query strings always are). If a user now queries the url with paramX, it will not throw an error, as the field will not be verified by typebox. Is there any way to handle a catch all for all parameters/body entries that are not part of the schema or is this something you would implement in nitro natively?

A current nitro project cannot be compiled because of the dependency to h3 0.7.21. h3 had breaking chages with 0.8.0, which leads to compilation errors:

import { eventHandler, setHeaders, sendRedirect, defineEventHandler, handleCacheHeaders, createEvent, getRequestHeader, createError, createApp, createRouter as createRouter$1, lazyEventHandler, toNodeListener } from 'h3';
                                                                                                                                                                                                   ^^^^^^^^^^^^^^
SyntaxError: The requested module 'h3' does not provide an export named 'toNodeListener'

We should at least update the dependency to 0.8.0 and continuously update the h3 dependency until it reaches 1.0.0 in CI/CD. Maybe add renovate to stay up to date?

PS: @kevinmarrec can you add the hacktoberfest label to the repo? Contributions can then be added to the contributors hacktoberfest score :)