Permit.Absinthe v0.2.0 graduates from proof-of-concept to production-ready, bringing the Permit authorization library's load-and-authorize pattern to Absinthe GraphQL in Elixir. Key additions include a rich set of customization options on the `permit` macro: `base_query` and `finalize_query` for Ecto query control, `fetch_subject` for custom user extraction, `handle_unauthorized`/`handle_not_found` error callbacks, a custom `loader` for non-Ecto sources, and a `wrap_authorized` post-authorization hook. The release also adds custom ID field support, a Dataloader integration via `authorized_dataloader/3` for batched association loading, and a reference table to help developers choose between resolver, middleware, directive, and Dataloader integration points. The schema-wide hydrator remains a work in progress. The API is still 0.x with possible breaking changes before 1.0.

8m read timeFrom curiosum.com
Post cover image
Table of contents
A quick refresher: what Permit.Absinthe doesWhat's new in v0.2.0Choosing the right integration pointWhat this means: exiting proof-of-conceptA note on API stabilityGet involved

Sort: