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

Remove TODO comment about warning on setting instead of pushing #2823

Merged
1 commit merged into from Dec 7, 2019

Conversation

bronzdoc
Copy link
Member

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.

@simi
Copy link
Member

simi commented Jun 30, 2019

If only specs are related to this, I think we should think about removing/deprecating those methods.

@bronzdoc bronzdoc added the wip label Jul 10, 2019
@bronzdoc
Copy link
Member Author

@simi if we deprecate/remove those methods people will have to modify their gemspecs to use << instead of = I'm not sure that change is something we want?

@duckinator
Copy link
Member

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?

@simi
Copy link
Member

simi commented Dec 7, 2019

@duckinator I did the same mistake, sorry.

@duckinator
Copy link
Member

@simi it's all good. 🙂

@bronzdoc since it's still marked WIP, I'm leaving this alone. If you're done with it, go ahead and merge it. 👍

@bronzdoc
Copy link
Member Author

bronzdoc commented Dec 7, 2019

specs is used across the Rubygems codebase to denote specifications. Sorry for the confusion!

@bronzdoc
Copy link
Member Author

bronzdoc commented Dec 7, 2019

@bundlerbot r+

ghost pushed a commit that referenced this pull request Dec 7, 2019
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>
@ghost
Copy link

ghost commented Dec 7, 2019

Build succeeded

  • macos (2.4.x)
  • macos (2.5.x)
  • macos (2.6.x)
  • ruby_master
  • ubuntu (2.4.x, bundler)
  • ubuntu (2.4.x, rubygems)
  • ubuntu (2.5.x, bundler)
  • ubuntu (2.5.x, rubygems)
  • ubuntu (2.6.x, bundler)
  • ubuntu (2.6.x, rubygems)
  • ubuntu_bundler_master (2.6.x)
  • ubuntu_lint
  • ubuntu_rvm (2.3.8)
  • ubuntu_rvm (jruby-9.2.9.0)
  • ubuntu_rvm (ruby-head)
  • windows (2.4.x)
  • windows (2.5.x)
  • windows (2.6.x)

@ghost ghost merged commit 1b7c4ca into master Dec 7, 2019
@ghost ghost deleted the remove_todo_about_warning branch December 7, 2019 14:29
This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants