Minimal authorization through OO design and pure Ruby classes
https://github.com/varvet/pundit
559 forks.
7.292 stars.
33 open issues.
Recent commits:
- CI: Use JRuby 9.2.17.0 (#677), GitHub
- Merge pull request #678 from varvet/build-against-trufflerubyBuild against Truffleruby head, GitHub
- Build against Truffleruby headTruffleruby is a high-performance implementation of Ruby: https://github.com/oracle/trufflerubyWe don't want to be responsible for supporting it, so it goes in theallow-failures section., Duncan Stuart
- Merge pull request #676 from varvet/drop-ruby-before-2_6Build against currently supported rubies, GitHub
- Build against currently supported rubies…and use the latest (2020) Travis build environment: focal2.6 is the earliest currently supported Ruby version: https://www.ruby-lang.org/en/downloads/branches/The focal environment doesn't seem to support openjdk 8. Here's thefailure from the build: install-jdk.sh 2020-06-02 Expected feature release number in range of 9 to 17, but got: 8 The command "~/bin/install-jdk.sh –target "/home/travis/openjdk8" –workspace "/home/travis/.cache/install-jdk" –feature "8" –license "GPL" –cacerts" failed and exited with 3 during .It looks like JRuby 9.1 isn't under development: the last release was in2018, and it's described as being "compatible with Ruby 2.3.x", which isa very old version . It feels OK to drop it.JRuby 9.2 says it's "compatible with Ruby 2.5.x", but it's the latestJRuby version so it seems like something we should keep., Duncan Stuart
https://www.sitepoint.com/straightforward-rails-authorization-with-pundit/
Rails >= 3 pry initializer
https://github.com/rweng/pry-rails
78 forks.
1.274 stars.
21 open issues.
Recent commits:
- Merge pull request #119 from CHTJonas/patch-1Update prompt syntax for Pry v0.13.0, GitHub
- Update prompt syntax for Pry v0.13.0Version 0.13.0 of Pry changed the way that prompts are configured and added. Specifically, setting the prompt via an array of two procs is now deprecated. This commit updates the README documentation so that warnings are no longer emitted when running `rails console` at the command line and fixes #118.See the Pry CHANGELOG for more information:https://github.com/pry/pry/blob/master/CHANGELOG.md, GitHub
- Bump to v0.3.9, Ryan Fitzgerald
- Add Rails 5.2 and 6.0 to build, fixing up issuesIn addition to adding scenarios for 5.2 and 6.0, I had to do somecleanup to get everything working well:* Replace string-based version checks with numeric ones, and update all version checks to treat 6+ the same as 5 (except where necessary).* Avoid touching `ActiveSupport::Deprecation::DeprecationProxy` instances to fix a couple of warnings in Rails 6.* Update Bundler as part of container setup, because Rails 6's config seems to rely on a newer version of Bundler than the one that comes with the Ruby image.* Update the regexes in the `show-routes` spec to be compatible with 5.2 and up.* Add a new code path to `show-routes` for Rails 6.* Upgrade all bundles, just for hygiene., Ryan Fitzgerald
- Merge pull request #109 from bitaculous/deprecation_warning_rails_6Use `module_parent_name` instead of `parent_name` for Rails 6., GitHub
Full Stack Developer, DevOps, CSM e LKU. coutoarmando@gmail.com