Permalink
Commits on Aug 10, 2012
  1. Version bump [ci skip]

    Nathan Long committed Aug 10, 2012
  2. Merge pull request #10 from nathanl/allow_options_hash

    Allow options hash
    committed Aug 10, 2012
  3. Updated README to show options

    [ci skip]
    Nathan Long committed Aug 10, 2012
  4. Allow authorization with options hash

    Nathan Long committed Aug 10, 2012
Commits on Aug 7, 2012
  1. Updated TODO - use i18n [ci skip]

    Nathan Long committed Aug 7, 2012
Commits on Jul 10, 2012
  1. Some TODO notes [ci skip]

    Nathan Long committed Jul 10, 2012
Commits on Jul 6, 2012
  1. README fixes.

    [ci skip]
    Nathan Long committed Jul 6, 2012
  2. Updated TODO and README

    [ci skip]
    Nathan Long committed Jul 6, 2012
Commits on Jun 26, 2012
  1. README update

    committed Jun 26, 2012
Commits on Jun 16, 2012
  1. Release 2.0.1

    committed Jun 16, 2012
  2. Fiddly little comment tweaks

    committed Jun 16, 2012
Commits on May 18, 2012
  1. Controller name should be plural

    Nathan Long committed May 18, 2012
Commits on May 12, 2012
  1. Merge branch 'master' of github.com:nathanl/authority

    Nathan Long committed May 12, 2012
  2. Improve comment

    Nathan Long committed May 12, 2012
  3. Won't implement.

    This is impossible in some cases, hard in others,
    and maybe be undesirably magical anyway.
    
    For instance, if someone wanted to do
    `link_to(@post)`, we could *maybe* determined the
    controller action and method and figure out if
    that's authorized or not. But if they do
    `link_to ('Search', 'http://www.google.com')`,
    there is truly no way for Authority to authorize
    that. So `authorized_link_to` would not be usable
    in that case, and it's unclear what it should do.
    
    Finally, if the developer does the normal
    `link_to(@post) if current_user.can_read?(@post)`,
    it's clear to him/her how Authority will answer
    that question. But with `authorized_link_to`,
    there would be a layer of magic in determining
    which permission to check, which would make this
    harder to understand and debug.
    
    So: not gonna do it.
    Nathan Long committed May 12, 2012
  4. Done - thanks to @scottmartin

    Nathan Long committed May 12, 2012
Commits on May 9, 2012
  1. Merge pull request #8 from scottmartin/master

    Fixed Controller Example
    committed May 9, 2012
  2. Update README.markdown

    scottmartin committed May 9, 2012
Commits on May 2, 2012
  1. Mentioned methods on `SecurityViolation`

    Nathan Long committed May 2, 2012
Commits on Apr 30, 2012
  1. README tweaks for clarity (thanks, @michaeltherobot)

    Nathan Long committed Apr 30, 2012
  2. Bump version

    Nathan Long committed Apr 30, 2012
  3. Don't warn when we're testing

    Nathan Long committed Apr 30, 2012
  4. SecurityViolation exposes more info

    Nathan Long committed Apr 30, 2012
  5. Squashed commit: models assume ApplicationAuthorizer;

    install task generates it.
    Nathan Long committed Apr 30, 2012
  6. Ignore Vim swap files

    Nathan Long committed Apr 30, 2012
Commits on Apr 26, 2012
  1. Merge pull request #7 from kevmoo/master

    run travis across supported versions of rails
    committed Apr 26, 2012
Commits on Apr 25, 2012
  1. update travis to tell all rails 3.x versions

    travis defaults to 'rake' for script, so it's not needed
    kevmoo committed Apr 25, 2012
  2. Add Gemnasium status badge

    Nathan Long committed Apr 25, 2012
  3. Updated TODO list

    Nathan Long committed Apr 25, 2012
  4. Merge pull request #6 from kevmoo/master

    gemspec and test tweaks
    committed Apr 25, 2012