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

Better naming? #4

Closed
shaqq opened this issue Mar 16, 2015 · 11 comments · Fixed by #6
Closed

Better naming? #4

shaqq opened this issue Mar 16, 2015 · 11 comments · Fixed by #6

Comments

@shaqq
Copy link

shaqq commented Mar 16, 2015

re: ruby-grape/grape#404 (comment)

I was a little confused about this gem being related to Rails. Maybe hashie-active-support?

@dblock
Copy link
Collaborator

dblock commented Mar 16, 2015

We were just discussing this on another mailing list. Maybe hashie-forbidden-attributes even? Suggest more.

@Maxim-Filimonov
Copy link
Owner

How about hashie-strong-parameters? We probably should change dependency to be on strong_parameters gem not on active_support then.

@Maxim-Filimonov
Copy link
Owner

Just tried what @dm1try suggested. Looks like it can work without dependency on activesupport. @dblock do you see any reason to keep activesupport dependency?

@dm1try
Copy link

dm1try commented Mar 19, 2015

@Maxim-Filimonov change dependency to be on strong_parameters is not so good idea, it will be an extra dependency for new projects because "strong parameters" is part of ActiveModel already

so you need some conditional dependency(bundler does not allow those things, I think)

if ActiveModel.VERSION < VersionWithoutStrongParams
  add_runtime_dependency 'strong_params'
...

You can lock on a specific AM version in the future if permitted? interface will be changed to another one(I don't think so :))

BTW, I don't like the way in which Hashie::Mash expand the public interface using any_unexisting_method with suffix ?. In common case your gem solve this problem => hashie-free-permitted?-method 😄 , it will be work not only for strong_params) .

If Mash expand its interface in this way it should allow except option or smth similar..

UPD
Forgot, for me hashie-strong-parameters and hashie-forbidden-attributes are both acceptable.

@dblock
Copy link
Collaborator

dblock commented Mar 19, 2015

I merged that PR. @Maxim-Filimonov You should pick a name and go at renaming this!

@Maxim-Filimonov
Copy link
Owner

I've been reading Rubygems guides about naming gems
Looks like as it's extension to Hashie it should be called something like hashie-forbidden_attributes. I'll go with that rename then unless anyone has better idea

@dblock
Copy link
Collaborator

dblock commented Mar 20, 2015

👍

@dm1try
Copy link

dm1try commented Mar 20, 2015

:shipit:

@Maxim-Filimonov
Copy link
Owner

Ok renamed.
Haven't pushed to Rubygems yet. If all good with the other one I'll close this issue with deprecation PR

@dblock
Copy link
Collaborator

dblock commented Mar 20, 2015

Looks fine to me, made a minor README pr.

@Maxim-Filimonov
Copy link
Owner

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

Successfully merging a pull request may close this issue.

4 participants