Remove responders dependency#112
Merged
orlando merged 1 commit intoassembler:masterfrom Nov 23, 2015
Merged
Conversation
… isnt a dependency for apps running rails >= 4.2
Closed
Collaborator
|
Thanks for the PR, merging 🔥 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Rails 4.2 removes class level respond_to and respond_with. Currently to use the attachinary gem in a rails 4.2 app you have to add the responders gem as a dependency. This seems like an easier solution that adding responders as a hard dependency of the gem.
I tested that this works for my app, but it does not actually use the cors controller functionality so not all cases have been tested.