Simplify management of query parameters

[darrachequesne]

Hi!

If I understand correctly, one can already extract the query parameters with setRequestCallback():

// note: async is needed here, else an "Uncaught TypeError: this.requestHandler(...).then is not a function" exception is thrown
h3Server.setRequestCallback(async ({ header }) => {
  const url = new URL(header[":path"], "https://example.com");
  if (url.pathname === "/my-path/") {
    header[":path"] = url.pathname;

    // option 1: added on the header object
    header[":query"] = url.searchParams;

    return {
      path: url.pathname,
      header,
      status: 200,
      // option 2: added on the userData object
      userData: {
        query: url.searchParams
      }
    }
  }
  return { status: 404 };
});

Is that right? In that case, do you think it would make sense to include them directly on the HttpWTSession?

Thanks in advance.

Related: #279

[martenrichter]

Yes, it is right, and there exists also an automated test for this.
The problem is that the session object does not exist when this callback is called.
So the only way in the current architecture is to process it later.
Of course, one can think about additional information that is passed somehow to the session.
(My idea was to keep it simple at the lower level, and let other users or libs handle the parsing).