-
Notifications
You must be signed in to change notification settings - Fork 78
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
Consolidate Plug Locations #146
Consolidate Plug Locations #146
Conversation
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.
If we are going to move the files we should update the module names to reflect this change.
Do you have a recommendation? It appears that other plugs in this directory are named as such:
I'm assuming you want something like |
I was mostly referring to
I personally would for clarity, but I'd like to hear what @jeregrine and @snewcomer think
I don't think we want to start creating alias for backwards compatibility, maintaining that long term would be a nightmare. It's possible to cut a new release with a new version to signify breaking changes. |
Agreed. It'd be nice to do this if even just to give people a fair heads up (if even until the 1.0 release).
Edit: I'm going to hold off on this until someone chimes in on backward compatibility. |
Move these two plugs with their other friends. Note that this commit introduces a backwards incompatible change: it renames the `PlugResponseContentType` to `ResponseContentType`.
c048a5c
to
2eccf08
Compare
@doomspork after some silence on the matter I decided to make the changes you requested. |
@@ -0,0 +1,27 @@ | |||
defmodule JSONAPI.ResponseContentTypeTest do |
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.
@doomspork FYI added a test for this plug too, it was missing one.
@jherdman sorry! The run up the holidays is hectic around here. |
In beam-community#146 the `QueryParser` Plug was moved alongside its friends. Unfortunately its test wasn't moved too. Let's fix that.
Move these two plugs with their other friends.