-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Make HTTP::Handler a module #3708
Conversation
Before we hit 1.0 we usually don't care about introducing breaking changes. I'd directly make |
e2071a9
to
6bc72fb
Compare
@asterite made the changes! |
@@ -371,7 +375,8 @@ module Crystal::Playground | |||
end | |||
end | |||
|
|||
class EnvironmentHandler < HTTP::Handler | |||
class EnvironmentHandler | |||
include HTTP::Handler |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would leave a blank line after here
6bc72fb
to
4ec39e3
Compare
Because HTTP::Handler was just an interface, it is less restrictive on applications to be an includeable module rather than in inheritable class.
4ec39e3
to
42e88e5
Compare
If someone wants to cancel all those now useless Travis CI jobs that are queued, that would be nice :p I didn't mean to clog the tubes 😅 |
Even though this is a breaking change, the fix is easy (include instead of inherit). Let's do this! @andrewhamon Thank you! |
Because HTTP::Handler was just an interface, it is less restrictive on applications to be an includeable module rather than in inheritable class.
This is a proof of concept of what I mentioned in #3690