-
Notifications
You must be signed in to change notification settings - Fork 2
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
Better naming? #4
Comments
We were just discussing this on another mailing list. Maybe hashie-forbidden-attributes even? Suggest more. |
How about hashie-strong-parameters? We probably should change dependency to be on strong_parameters gem not on active_support then. |
Just tried what @dm1try suggested. Looks like it can work without dependency on activesupport. @dblock do you see any reason to keep activesupport dependency? |
@Maxim-Filimonov change dependency to be on so you need some conditional dependency(
You can lock on a specific AM version in the future if BTW, I don't like the way in which If UPD |
I merged that PR. @Maxim-Filimonov You should pick a name and go at renaming this! |
I've been reading Rubygems guides about naming gems |
👍 |
Ok renamed. |
Looks fine to me, made a minor README pr. |
re: ruby-grape/grape#404 (comment)
I was a little confused about this gem being related to Rails. Maybe hashie-active-support?
The text was updated successfully, but these errors were encountered: