All Versions
13
Latest Version
Avg Release Cycle
34 days
Latest Release
2709 days ago
Changelog History
Page 1
Changelog History
Page 1
-
v1.1.1
April 16, 2017 -
v1.1.0 Changes
November 15, 2016- Enhancements
- Add
non_id_actions
opt
- Add
- Enhancements
-
v1.0 Changes
- Bug fixes
- Do not clobber resources in the
Conn
on index action if they are of the same model
- Do not clobber resources in the
- Bug fixes
-
v0.14.2 Changes
July 16, 2016- Relax Ecto version requirements
-
v0.14.1 Changes
- Bug fixes
- Use Macro.underscore/1 instead of Mix.Utils.underscore/1 to avoid :mix dependency on production
- Bug fixes
-
v0.14.0 Changes
February 21, 2016- Enhancements
- You can now tell Canary to search for a resource using a field other than the default
:id
by using the:id_field
option. Note that the specified field must be able to uniquely identify any resource in the specified table.
- You can now tell Canary to search for a resource using a field other than the default
- Dependency changes
- Elixir ~> 1.2 is now required
- Ecto ~> 1.1 is now required
- Enhancements
-
v0.13.1 Changes
February 14, 2016- Enhancements
- If both an
:unauthorized_handler
and a:not_found_handler
are specified forload_and_authorize_resource
, and the request meets the criteria for both, the:unauthorized_handler
will be called first.
- If both an
- Bug Fixes
- If more than one handler are specified and the first handler halts the request, the second handler will be skipped.
- Enhancements
-
v0.13.0 Changes
- Enhancements
- Canary can now be configured to call a user-defined function when a resource is not found. The function is specified and used in a similar manner to
:unauthorized_handler
.
- Canary can now be configured to call a user-defined function when a resource is not found. The function is specified and used in a similar manner to
- Bug Fixes
- Disabled protocol consolidation in order for tests to work on Elixir 1.2
- Enhancements
-
v0.12.2 Changes
January 04, 2016- Deprecations
- Canary now looks for the current action in
conn.assigns.canary_action
rather thanconn.assigns.action
in order to avoid conflicts. Theaction
key is deprecated.
- Canary now looks for the current action in
- Deprecations
-
v0.12.1
January 01, 2016