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
Remove TODO comment about warning on setting instead of pushing #2823
Conversation
If only specs are related to this, I think we should think about removing/deprecating those methods. |
@simi if we deprecate/remove those methods people will have to modify their gemspecs to use |
This looks good to me, although I initially interpreted "specs" as referring to tests instead of gemspecs, which confused me for a moment. Realistically, I don't think these can be deprecated at this point. It'd break a ton of gemspecs in the wild. @bronzdoc is there a reason this is marked as wip, or is it good to go? |
@duckinator I did the same mistake, sorry. |
|
@bundlerbot r+ |
2823: Remove TODO comment about warning on setting instead of pushing r=bronzdoc a=bronzdoc # Description: Remove TODO comment about warning on setting instead of pushing. This methods are heavily used across specs and i personally think those warning at this point will not add much value, thoughts? ______________ I will abide by the [code of conduct](https://github.com/rubygems/rubygems/blob/master/CODE_OF_CONDUCT.md). Co-authored-by: bronzdoc <lsagastume1990@gmail.com>
Build succeeded
|
Description:
Remove TODO comment about warning on setting instead of pushing.
This methods are heavily used across specs and i personally think those warning at this point will not add much value, thoughts?
I will abide by the code of conduct.