Update omniauth dependency to support 1.0 and 2.0 #3
Conversation
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
1 participant
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.
At the moment, I can't install this gem alongside omniauth 2.0 because 2.0's rails_csrf_protection requires omniauth be at least 2.0. This PR lets you install this gem alongside omniauth 1.0 or 2.0.
It's worth noting that the official omniauth gems (in the omniauth org), e.g. omniauth-github, have simply changed
"~> 1.0"to"~> 2.0"and bumped the major version of their gem alongside it, but that's presumably because the gem itself required code changes. This one seems to work fine with omniauth 2.0, so I see no reason to bump its major version.