feat(server): agnostic http request handler

[fallenfreq]

Closes #4280 /
Closes T-26

🎯 Changes

What changes are made in this PR? Is it a feature or a bug fix?

1. You can now add custom servers without them having to have the same req.query type as express.
   ParsedQs interface has been removed for this because its only use becomes redundant if you can't guarantee that it can be passed to URLSearchParams

2. The middleware method that you pass to an adapter will now pass the correct types through to the "req" and "res" arguments.

3. Added the necessary tests to test the new features.

✅ Checklist

• ✅ I have followed the steps listed in the Contributing guide.
• ✅ If necessary, I have added documentation related to the changes made.
• ✅ I have added or updated the tests related to the changes made.

[vercel]

@fallenfreq is attempting to deploy a commit to the trpc Team on Vercel.

A member of the Team first needs to authorize it.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
trpc-next-app-dir	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jun 2, 2024 6:44pm
www	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jun 2, 2024 6:44pm

[KATT]

This unfortunately fails all tests

[KATT]

This unfortunately fails all tests

[KATT]

cc @fallenfreq could you get this to point to next instead? we're not really doing new features on main anymore

sorry for the delay on this!

[fallenfreq]

cc @fallenfreq could you get this to point to next instead? we're not really doing new features on main anymore

sorry for the delay on this!

Yeah, I'll be working on a project that uses trpc again very soon so i'll do it then.

[fallenfreq]

Hey @KATT, This is ready for review again. The original disputed property name is no longer required with trpc v11. I've updated the changes and tests to work with v11 so hopefully this is good to be merged into next now.

[KATT]

Please just delete this, we have plenty of tests that test this path

[fallenfreq]

Will do, this was originally testing the now redundant forceTrpcQueryFromUrl property as well but it's still testing that query parameters that don't match the express type don't throw and that the handler middleware has the types passed correctly. The other tests are just testing the implementation of the test itself.

[fallenfreq]

Hi @KATT, This was done 3 weeks ago, I know it said there were two extra failing tasks but I think that was just due to a token generation limit being reached for some of the tests. I've just updated it and those failing tests have passed.