1. 22 Apr, 2019 6 commits
  2. 07 Mar, 2019 1 commit
  3. 15 Feb, 2019 1 commit
  4. 11 Apr, 2018 2 commits
  5. 10 Apr, 2018 2 commits
  6. 09 Apr, 2018 1 commit
  7. 04 Apr, 2018 1 commit
  8. 29 Mar, 2018 3 commits
  9. 28 Mar, 2018 2 commits
  10. 23 Mar, 2018 1 commit
  11. 09 Jan, 2018 3 commits
  12. 05 Jan, 2018 3 commits
    • Merge pull request #433 from jhawthorn/notice · d446da46
      Add a very soft deprecation notice
      John Hawthorn committed
    • Add a very soft deprecation notice · d721f52c
      This isn't a change from how paranoia has been developed for the past
      few years, but makes it more explicit.
      
      I hope the recommendation against new projects using paranoia isn't too
      controversial. I think anyone who has used this gem extensively has been
      surprised by it many times. This is just the nature of replacing
      ActiveRecord's behaviour. I believe paranoia does extremely well given
      that it does that.
      
      A lot of developers will reach for paranoia or acts_as_paranoid because
      they're the first result they will find. However most users are just
      looking to hide or disable some records, and they would do much better
      to just toggle a flag rather than have paranoia override ActiveRecord's
      behaviour on their model.
      
      I hope linking to discard here isn't inappropriate, I believe it's the
      best resource describe the caveats of paranoia as well as give a good
      example of how to soft-delete without needing paranoia or
      acts_as_paranoid.
      John Hawthorn committed
    • Merge pull request #431 from mrhead/add-support-for-rails-5-2 · 021551fc
      Test with Rails 5.2
      John Hawthorn committed
  13. 29 Nov, 2017 1 commit
  14. 03 Nov, 2017 3 commits
  15. 02 Nov, 2017 10 commits