Releases: danschultzer/coherence_assent
Releases · danschultzer/coherence_assent
v0.4.0
04 Sep 16:55
Compare
Sorry, something went wrong.
No results found
Backwards incompatible changes
Coherence v0.5.2 or above required #20
v0.3.2
04 Sep 15:37
Compare
Sorry, something went wrong.
No results found
Changes
Coherence restricted to v0.5.0 as v0.5.1 introduces various breaking changes #20 #22
v0.3.1
19 Mar 21:26
Compare
Sorry, something went wrong.
No results found
Bug fixes
Github works again (tests have been improved) #12
v0.3.0
06 Mar 23:27
Compare
Sorry, something went wrong.
No results found
Bug fixes
Facebook now works correctly with app secret and email field #11
Changes
Refactoring and specs #10
Backwards incompatible changes
Renamed CoherenceAssent.Strategies.OAuth to CoherenceAssent.Strategy.OAuth #10
Renamed CoherenceAssent.Strategies.OAuth2 to CoherenceAssent.Strategy.OAuth2 #10
v0.2.5
04 Mar 22:18
Compare
Sorry, something went wrong.
No results found
Changes
Allow for a custom table name in UserIdentity schema #9
v0.2.4
13 Feb 01:11
Compare
Sorry, something went wrong.
No results found
Changes
User identities on resource owner now default with on_delete: :delete_all #6
Bug fixes
Now works when confirmable is not enabled in Coherence #5
v0.2.3
13 Jan 20:05
Compare
Sorry, something went wrong.
No results found
Changes
Require login for delete instead of destroy in AuthController
Improved test scenarios
v0.2.2
13 Jan 18:33
Compare
Sorry, something went wrong.
No results found
Changes
Fixed issue in Github strategy where the get_email didn't passthrough error message
Added VK.com strategy
v0.2.1
04 Nov 17:22
Compare
Sorry, something went wrong.
No results found
v0.2.0
04 Nov 05:26
Compare
Sorry, something went wrong.
No results found
Breaking changes
All strategies has had the following methods updated:
authorize_url(conn: conn, config: config) -> authorize_url(conn, config)
callback(conn: conn, config: config, params: params) -> callback(conn, config, params)
Changes
authorization_params are now included when obtaining the access token in the OAuth 2.0 strategy.