All Versions
Latest Version
Avg Release Cycle
34 days
Latest Release
2351 days ago

Changelog History
Page 2

  • v0.12.0 Changes

    January 01, 2016
    • โœจ Enhancements
      • Canary can now be configured to call a user-defined function when authorization fails. Canary will pass the Plug.Conn for the request to the given function. The handler should accept a Plug.Conn as its only argument, and should return a Plug.Conn.
      • For example, to have Canary call Helpers.handle_unauthorized/1: elixir config :canary, unauthorized_handler: {Helpers, :handle_unauthorized}
      • You can also specify the :unauthorized_handler on an individual basis by specifying the :unauthorized_handler opt in the plug call like so: elixir plug :load_and_authorize_resource Post, unauthorized_handler: {Helpers, :handle_unauthorized}
  • v0.11.0 Changes

    December 22, 2015
    • โœจ 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 Changes

    • ๐Ÿ› Bug fix

      • Correctly checks conn.assigns for pre-existing resource
    • ๐Ÿ—„ Deprecations

      • Canary now favours looking for the current action in conn.assigns.canary_action rather than conn.assigns.action in order to avoid conflicts. The action key is deprecated
    • โœจ Enhancements

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