Feature request: allow customizing Server Function HTTP method

[Coretteket]

Currently, all requests done on the client-side for a server$ function are POST requests. This makes sense as a default, but there are many possible use-cases for server$ for simply querying data, where a GET request would be more appropriate. This is not just semantics, with the problem I run into the impossibility of caching server$ requests on Vercel's Edge Network. Therefore, I would appreciate the option to select a different HTTP method. For context, I raised this issue for pRPC (OrJDev/prpc#73), which uses server$ for a query$ function under the hood, which therefore is limited by Solid Start.

[ryansolid]

We've implemented this in Bling. It will make it's way to SolidStart.

[Coretteket]

Awesome – can't wait!

[Download]

Not sure why POST would even make sense as the default, actually...

What is the default of HTML (<form> tag without method specified)?: GET
What is the default CURL uses?: GET
What is the default of fetch?: GET

IMHO there is only one sane default for requests and that is GET...

Oh and it is not just Vercel's Edge Network. The same is true for .e.g. CloudFlare. For the same reason you should avoid adding Set-Cookie header to all responses (they won't be cached), or Authorization header to every request... A lot of servers out there are effectively disabling caching...

[lxsmnsyc]

@Download The only reason POST makes sense is because the server functions utilizes the request body, something that GET cannot offer. However, GET can be potentially supported, ideally if the function has no arguments or if the arguments can be safely encoded in the url.

Other methods should work just fine

[ryansolid]

This has been implemented in SolidStart in 0.5.x via the GET method.