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

Update to a more extensible deprecation method. #1043

Conversation

BobbyMcWho
Copy link
Contributor

@BobbyMcWho BobbyMcWho commented Sep 30, 2019

The previous implementation would not warn about deprecation upon being inherited, and warned in stdout. Upon initialization or Inheritance, this implementation warns in stderr similar to Gem::Deprecate, but gives a semver instead of a date like the default Gem::Deprecate does.

@@ -59,4 +59,4 @@ def certificate_store
end
end

EventMachine::HttpStubConnection.send(:include, EmHttpSslPatch)
EventMachine::HttpStubConnection.include(EmHttpSslPatch)
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Rubocop made me do it 🚓 🤖

end

it 'does not raise an error for inherited error-namespaced classes but prints an error message' do
error_message, = with_warn_squelching { class E < Faraday::Error::ClientError; end }
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this looks like a typo, but it's not. Rubocop likes
a, = [:foo, :bar] better than
a, _ = [:foo, :bar] 🤷‍♂

@BobbyMcWho BobbyMcWho mentioned this pull request Oct 1, 2019
2 tasks
The previous implementation would not warn about deprecation upon
being inherited, and warned in a stdout. This implementation warns
in stderr similar to Gem::Deprecate, but gives a semver instead of
a date like the default Gem::Deprecate does.
@BobbyMcWho BobbyMcWho force-pushed the create-extensible-faraday-deprecate branch from fe63747 to cd7888f Compare October 1, 2019 16:49
@technoweenie technoweenie added this to In progress in v1.0 via automation Oct 14, 2019
@technoweenie technoweenie moved this from In progress to Review in v1.0 Oct 14, 2019
v1.0 automation moved this from Review to Done Oct 15, 2019
@technoweenie technoweenie mentioned this pull request Oct 15, 2019
4 tasks
@technoweenie
Copy link
Member

FYI: This closed because I killed the 0.16.x branch. I've opened #1052 to create a 0.17.x release branch and port this PR over.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
No open projects
v1.0
Done
Development

Successfully merging this pull request may close these issues.

None yet

2 participants