View Source Changelog
unreleased
Unreleased
1-0-1-2022-11-06
[1.0.1] - 2022-11-06
changed
Changed
- Use
Keyword.pop/3
with default value instead ofKeyword.pop!/2
, so that you can pass options toLetMe.redact/3
without passing theredact_value
option.
1-0-0-2022-11-06
[1.0.0] - 2022-11-06
added
Added
- Added
LetMe.Policy.filter_allowed_actions/3
andLetMe.filter_allowed_actions/4
. - Added
LetMe.Policy.get_object_name/1
.
changed-1
Changed
- Renamed
c:LetMe.Policy.authorized?/3
toLetMe.Policy.authorize?/3
, because consistency is more important than grammar, maybe. - The
c:LetMe.Schema.scope/2
callback was removed in favour ofLetMe.Schema.scope/3
. The__using__
macro defined default implementations for both functions that returned the given query unchanged, in case you only needed theredact
callback of the behaviour. In practice, this made it all too easy to call the 2-arity version when only the 3-arity version was defined, and vice versa, which would lead the query to not be scoped. So in order to reduce the room for error at the cost of a minor inconvenience, you will now always need to implement the 3-arity function, even if you don't need the third argument. - Changed
c:LetMe.Schema.redacted_fields/2
toLetMe.Schema.redacted_fields/3
to allow passing additional options, and to be consistent withLetMe.Schema.scope/3
.
0-2-0-2022-07-12
[0.2.0] - 2022-07-12
changed-2
Changed
- Added support for nested field redactions, either by explicitly listing the
fields or by referencing a module that also implements
LetMe.Schema
.
fixed
Fixed
reject_redacted_fields/3
calledredact/2
callback with the wrong argument order.
0-1-0-2022-07-11
[0.1.0] - 2022-07-11
initial release