Change Log¶
Version 0.7 (2018-XX-XX)¶
- Added
flask_allows.view.guard_entireandflask_allows.views.exempt_from_requirementsto make protecting entire blueprints easier. - Added
__all__export markers to flask_allows modules to prevent accidental re-export of other symbols when usingfrom flask_allows.module import *
Version 0.6 (2018-05-26)¶
Permissionno longer needs an application context for construction but does require one for evaluation now.- Added
Allows.runa public helper that performs the complete fulfill and fail cycle. This cleans up the duplication betweenAllows.requires,requiresandPermission.__enter__ - Removed
Permission.throw_type - Removed
PermissionedView,PermissionedMethodView - Added ability to disable requirements already registered on routes and inside
handlers via the
flask_allows.overrides.OverrideManagerclass - Added ability to add more requirements to be run during checks on routes
and other handlers via the
flask_allows.additional.AdditionalManagerclass
Version 0.5.1 (2018-04-22)¶
- Added
wants_requestto ease transition to user only requirements
Version 0.5 (2018-04-17)¶
- Real documentation
- Accepting request in requirements is now deprecated, pending removal in 1.0
- Promoted internal
_allowscontext local to part of the public interface - Bug Fix: ConditionalRequirement returned False when no requirements were provided
- it now returns True and mimics the behavior of
allbetter
Version 0.4 (2017-08-29)¶
- Clarify deprecation message for PermissionedView, will be removed in 0.6
- Deprecate Permission.throw_type for 0.6 removak
- Add optional on_fail for allows.requires and requires decoration
- Fix coverage path problem with local testing
Version 0.3.2 (2017-08-29)¶
- Fix package data not being included
Version 0.3.1 (2017-08-20)¶
- Fix error that prevent sdist builds on 2.7
Version 0.3 (2017-08-20)¶
- Drop official support for Python 3.3
- Deprecate implicit decoration on class based views via the requirements attribute