Tim
Tim
Might be a supabase issue? https://github.com/supabase/supavisor/issues/85
dfx doesn't modify the rest responses to keep the maintenance burden low. I think most of the permission helpers accept string or bigint.
In that case you would just do `Number(Perms.fromList(["Administrator"]))`, I don't think that is too bad.
A better approach is allowing a raw client to be passed in. But I'm not sure about this, as currently the client is protected with a semaphore to ensure exclusive...
HttpApiMiddleware will have a type-level requires option: https://github.com/Effect-TS/effect-smol/blob/main/packages/effect/src/unstable/httpapi/HttpApiMiddleware.ts#L173 It could be back-ported at some stage.
I think a udp abstraction is worth adding :) I need to set aside some time to look at this and work out if is going in the right direction.
This is the intended behaviour, as it only inspects the service at the type level. The jsdocs could be updated if they don't mention this.
While they are part of the type, you can't cover off non-effect properties without introducing code generation.
Can we overload the predicate return type of `filterMapEffect` to be `Option | Effect` I wonder. The only case that could cause issues is if you return `Option`.
`Stream.filterMapEffectOption`?