Skip to content

CHANGELOG.md

Latest commit

 

History

History
111 lines (73 loc) · 4.6 KB

CHANGELOG.md

File metadata and controls

111 lines (73 loc) · 4.6 KB
Raw

Changelog

== Version 1.0.0beta1

  1. Initial version

== Version 1.0.0rc1

  1. Fix bug where user can't check on class
  2. Adding new clause: cant_all

== Version 1.0.0rc2

  1. Fix bug when class's name, as a constant, is reloaded (re-allocated to different address in the memory)
  2. Allow describing rule for nil, useful if user is not authenticated thus role is probably nil
  3. Remove pry from development dependency

== Version 1.0.0rc3

  1. Each target class should includes Bali::Objector, for the following reasons:
    • Makes it clear that class do want to include the Bali::Objector
    • Transparant, and thus less confusing as to where "can?" and "cant" come from
    • When ruby re-parse the class's codes for any reasons, parser will be for sure include Bali::Objector
  2. Return true to any can? for undefined target/subtarget alike
  3. Return false to any cant? for undefined target/subtarget alike

== Version 1.0.0

  1. Released the stable version of this gem

== Version 1.1.0rc1

  1. Ability for rule class to be parsed later by passing later: true to rule class definition
  2. Add Bali.parse and Bali.parse! (Bali.parse! executes "later"-tagged rule class, Bali.parse executes automatically after all rules are defined)
  3. Added more thorough testing specs
  4. Proc can be served under unless for defining the rule's decider

== Version 1.1.0rc2

  1. Ability to check can? and cant? for subtarget with multiple roles
  2. Describe multiple rules at once for multiple subtarget

== Version 1.2.0

  1. Passing real object as subtarget's role, instead of symbol or array of symbol
  2. Clause can also yielding user, along with the object in question

== Version 2.0.0rc1

  1. Bali::AuthorizationError subclass of StandardError tailored for raising error regarding with authorisation
  2. new objectors can! and cannot! to raise error on inappropriate access

== Version 2.0.0

  1. Release!

== Version 2.1.0

  1. others block would allow for rule definitions within it to be applied for all undefined subtargets of a target
  2. Fixing bug when roles_for of a user object retrieves nil as the user's role, it won't acknowledge that the user is indeed having nil-role and raising an error instead.
  3. Inherits rules by passing :inherits option when defining rules_for
  4. clear_rules within describe or others block to remove all inherited rules (or any rules previously defined) for that subtarget
  5. Adding Bali::Printer that would enable for rules to be printed by calling .pretty_print on it

== Version 2.1.1

  1. Bug fixes on clear_rules which it clear rules defined in others even when not asked to
  2. Bug fixes on Bali::Printer where inherited rules print the wrong target class due to another bug in an internal file (but doesn't hamper rules-checking logic)

== Version 2.1.2

  1. nil will be printed when objecting with can! or cannot! for better readability.
  2. Bug fixes on declaring multiple rules with decider. Previously, others were ignored--now, every single rule will get defined whether decider is present or not.

== Version 2.2.0

  1. Deprecating describe block in favour of role block, describe is to be deprecated in version 3.0.
  2. Using strategy pattern, heavy refactoring
  3. Human-readable authorisation error message when invoking !-version of can/cannot, for eg: Role general_user is not allowed to perform operation update on My::Transaction

== Version 2.4.0 (March 1, 2016)

  1. rules_for accepting String instead of consanttised class name, in case the class is not yet loaded

== Version 6.0.0rc1 (Apr 26, 2020)

  1. Integration with Rails is expected
  2. Removed bang methods: can!, cannot!. can? and cant? should be enough. User can raise an error by themselves as necessary.
  3. Change back from cannot to cant
  4. Removing: Bali.map_rules and its auxiliary functions
  5. Use class for defining rules
  6. Hook to ActiveModel without having to include Bali::Authorizer

== Version 6.0.0rc2 (Apr 27, 2020)

  1. Hook into ActionView and ActionController
  2. Not storing the ruler class inside a RULE_CLASS_MAP to avoid caching it
  3. Not storing the role field mapper inside a TRANSLATED_SUBTARGET_ROLES

== Version 6.0.0rc3 (May 01, 2020)

  1. Built-in be_able_to matcher for RSpec
  2. Renaming Bali::Printer.pretty_print to Bali::Printer.printable
  3. Uniform can? and cant? authorizization checker
  4. Adding scope block

== Version 6.0.0

  1. Bug fix for can? and cant? when passing 2 arguments.

== Version 6.0.1

  1. Bug fix for judgement issue when the user's role is an empty array