🚀 Feature Proposal

Could it be possible to support an optional case insentive option for query parameters? Adding the option caseSensitive: false does not seems to impact query parameters

Motivation

For backward compatibilitites you sometime need to support multiple casing

Example

With that code

fastify.get<{ Querystring: { test: string } }>(
    "/caseinsensitiv

Feedback from @surma:

I feel like by default you should add a rootMargin to the IO to trigger the load before something comes into the viewport.

So, rootMargin defaults to "0px 0px 0px 0px", meaning the intersection will be computed between the root element's unmodified bounds rectangle and the target's bounds. This change would be made to https://github.com/GoogleChromeLabs/quicklink/b

You have already researched for similiar issues?

Yes, and mine is somewhat similar to this one : fastify/fast-json-stringify#175

What are you trying to achieve or the steps to reproduce?

Context:

I am using fastify with default options.
I am using a schema to validate and serialize the output of my API endpoint.
This schema includes a oneOf betwe