Laytan issues

Results 62 issues of


                                            Laytan

Middlewares (including routing) can be seperate packages as they have no internal logic

enhancement

server

`Request.url` should not be parsed if not used, make it `Request._url` and add `request_url`

server

performance

Simple CSRF middleware

enhancement

server

Simple session middleware

enhancement

server

Figure out a nice way to pass variables/context from the middlewares to the handlers

Not sure of a good solution, the size and amount should arbitrary because there are numerous middleware applications, which is probably not possible in a type safe manner, I'm thinking...

enhancement

server

Handlers should take one argument with the request and response inside it

This allows the user to easily put this in a user_data argument or on the context, which would be harder if it were 2 separate arguments.

enhancement

server

Client body parsing should look more like that of the server

The server has a much better API for parsing the request body. Although the client can't assume that the context.temp_allocator is the one that should be used, so it needs...

enhancement

client

Client should remember resolved DNS

enhancement

client

Client should be able to follow redirects

enhancement

client

make structs with multiple fields always return indirect in wasm c abi

we already have a special case for this in `type_can_be_direct` but it was overwriting that decision here, also had a bug where it was setting the calling convention after computing...