Clément Delafargue
Clément Delafargue
i have opened a poll: https://framapiaf.org/@clementd/110616658721525331
i have a proof of concept here https://github.com/biscuit-auth/biscuit-rust/pull/188 the proof-of-concept makes them _non-strict_ rather than _lazy_. The difference is subtle (and not observable from the outside in the absence of...
Thanks! I guess that apart from `authorize`, the other candidates are all functions depending on keypair generation, which could indeed be relaxed to `MonadRandom`. Do note that there is planned...
> BTW, our use case is that we have Polysemy actions running in Servant Have you looked at biscuit-servant yet? My plan was to try it out with an effect...
> We are indeed looking at biscuit-servant. At first glance, it would seem useful if we can use biscuit verification without needing effects like `Embed IO` or `Final IO` in...
👋 I might have time to assist if you want to try and express the timeout check through a typeclass constraint, that could be discharged by IO itself, or by...
Hi, thanks for the report! So currently the workaround would be to create an authorizer and call authorize before querying it. I think that the go library could benefit from...
A few propositions: ## Syntax - use `[]` for lists - use `{ : }` for maps, where `` and `` can be an arbitrary datalog term - use `{}`...
LGTM. tbf the whole Token::Error hierarchy would need a refresh
The capi build failure is being worked on, I think