Théophile Choutri de Tarlé
Théophile Choutri de Tarlé
@jaspervdj Alright, that's going to be fun then :P
@jaspervdj I've opened a PR to track my work, but I have to admit some the code in `Step.Data` is a bit nebulous when discovering the codebase. Especially this code:...
@jaspervdj hi! other duties came in the way, but I'll resume my work starting next week. I'll drop you an email if needs be. :)
Any reason we can move on this, as Bullseye was released on September 20th?
Hi @jhmcstanton! Thank you very much for this PR. In concertation with @gdeest and @akhesaCaro, we have come to the conclusion that this type ought to be a newtype, so...
Here are the aspects to take into account when implementing this: 1. How are fetched the auth information (token, cookie, etc) * This must be provided by our package, be...
Here is a prototype design that would be nice to have ```haskell {- ## Example type API = Authenticate User (AuthCookie :> AuthHeader "X-Scrive-XToken") :> ToServantApi API' type API =...
From what I am reading, it would seem that the optimal direction would be to iterate massively over generalised auth, get it out of Experimental, provide use-cases like: ### On...
Update: I have been working (with the help of @divarvel) on a term-level workflow for endpoints that allow optional authentication and endpoints that require authenticated callers. @Vlix The solution I'm...
> I've taken this approach mainly because that's how servant seems to do things (i.e. ReqBody' mods ctypes a). You are absolutely right, but then it has two negative effects:...