Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release 1.0 #14

Open
inossidabile opened this issue Jul 13, 2013 · 4 comments
Open

Release 1.0 #14

inossidabile opened this issue Jul 13, 2013 · 4 comments
Labels

Comments

@inossidabile
Copy link
Owner

I need more success stories than my own one to ensure everything works properly or close to it to release 1.0. Please, put 👍 into this thread if you have one and you agree 1.0 can be released.

Additional enhancements that I would like to see prior to 1.0:

  • Strong Parameters integration
  • CanCan integration (as a gem)
  • InheritedResources integration (as a gem)
  • Better tutorial on how to use Protector + StrongParameters + CanCan (or InheritedResources) with Rails 4
  • Mongoid integration?
@fdeschenes
Copy link
Contributor

+1

I'm using Protector in a few different projects and all seems to be working properly for me too – although I haven't had a chance to test the Strong Parameter and CanCan integrations.

@m4tm4t
Copy link

m4tm4t commented Aug 11, 2013

👍 I'm just trying protector & rails 4. Everything is ok.
About concerns, I tried something like that https://gist.github.com/foohey/6204053 .
Is the right implementation ?

@inossidabile
Copy link
Owner Author

Yep, looks like it's fine.

@toxix
Copy link
Contributor

toxix commented Jan 15, 2015

This is the only gem I know which allowing me to restrict the active-record reading acces on a per field basis. Thank you for all your work. 🌟

(Also tried Consul, Pundit)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants