Packages

canary

0.12.1
2.0.0-dev 1.2.0 1.1.1 1.1.0 1.0.0 0.14.2 0.14.1 0.14.0 0.13.1 0.13.0 0.12.2 0.12.1 0.11.0 0.10.4 0.10.1 0.10.0 0.9.1 0.9.0 0.8.0 0.7.0 0.6.0 0.5.1 0.5.0 0.4.0 0.3.0 0.2.0 0.1.0

An authorization library to restrict what resources the current user is allowed to access, and load those resources for you.

HexDocs

Current section

Files

Jump to
Readme
27 Versions
3 Dependencies
0 Dependants
Files
Activity
canary CHANGELOG.md
Raw

CHANGELOG.md 

## Changelog



## v0.12.0



* Enhancements

  * Canary can now be configured to call a user-defined function when an action is unauthorized



## v0.11.0



* Enhancements

  * Resources can now be loaded on `:new` and `:create` actions, when `persisted: true` is specified in the plug call. This allows parent resources to be loaded when a child is created. For example, if a `Post` resource has multiple `Comment` children, you may want to load the parent `Post` when creating a new `Comment`. You can load the parent `Post` with a separate

  ```elixir

  plug :load_and_authorize_resource, model: Post, id_name: "post_id", persisted: true, only: [:create]

  ```

  This will cause Canary to try to load the corresponding `Post` from the database when creating a `Comment` at the URL `/posts/:post_id/comments`



## v0.10.0



* Bug fix

  * Correctly checks `conn.assigns` for pre-existing resource



* Deprecations

  * Canary will now favours looking for the current action in `conn.assigns.canary_action` rather than `conn.assigns.action` in order to avoid conflicts. The `canary_action` key is deprecated



* Enhancements

  * The name of the id in `conn.params` can now be specified with the `id_name` opt