Coverage remained the same at 85.507% when pulling e421bd22c395763f9e6a304096b0e9830e4330d6 on jastkand:lock-oauth2-version into d859ad83c47c70228cfdd99c953d9fc2bfafa66e on sobolevn:master.
Coverage remained the same at 85.507% when pulling e421bd22c395763f9e6a304096b0e9830e4330d6 on jastkand:lock-oauth2-version into d859ad83c47c70228cfdd99c953d9fc2bfafa66e on sobolevn:master.
Coverage remained the same at 85.507% when pulling e421bd22c395763f9e6a304096b0e9830e4330d6 on jastkand:lock-oauth2-version into d859ad83c47c70228cfdd99c953d9fc2bfafa66e on sobolevn:master.
This is a fix which was applied to most ueberauth strategy implementations to prevent problems with new version of oauth2.
This fix was used in this strategies: https://github.com/ueberauth/ueberauth_facebook https://github.com/ueberauth/ueberauth_github https://github.com/ueberauth/ueberauth_google https://github.com/ueberauth/ueberauth_slack
Fixes #9