-
Notifications
You must be signed in to change notification settings - Fork 36
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
Clarify rename message? #104
Comments
@Fryguy I created the change, but didn't have a place to merge into. Do you want to create a I was thinking: -warn "[DEPRECATION] This gem has been renamed to optimist and will no longer be supported. Please switch to optimist as soon as possible."
+warn "[DEPRECATION] The trollop gem has been renamed to optimist and will no longer be supported. Please switch to optimist as soon as possible." |
Sounds good to me @kbrock |
@kbrock I'm not sure how to submit a PR for this. I don't know how to target |
You can probably just push the commit directly...no need for a PR as we've discussed the wording here. |
thanks for your help. there is a |
I saw this deprecation message: "[DEPRECATION] This gem has been renamed to optimist and will no longer be supported. Please switch to optimist as soon as possible."
But nothing in that message says which gem has been renamed. It wasn't hard to google the message, but if it's easy enough to push a new version of trollop, maybe it could be worth clarifying by changing "This gem" to "The trollop gem".
The text was updated successfully, but these errors were encountered: