adding notes about pattern change as well as a better reference to fb-login example

docs/api_endpoints.rst

@@ -74,6 +74,7 @@ Basing on example from installation section :doc:`Installation </installation>`
 
     - access_token
     - code
+    .. note:: ``access_token OR code`` can be used as standalone arguments, see https://github.com/Tivix/django-rest-auth/blob/master/rest_auth/registration/views.py#L83
 
 - /rest-auth/twitter/ (POST)
 

docs/changelog.rst

@@ -4,6 +4,7 @@ Changelog
 0.8.0
 -----
 - added support for django-rest-framework-jwt
+- added support for django-allauth hmac email confirmation pattern
 
 0.7.0
 -----

docs/faq.rst

@@ -14,8 +14,11 @@ FAQ
 
     You should override this view/url to handle it in your API client somehow and then, send post to /verify-email/ endpoint with proper key.
     If you don't want to use API on that step, then just use ConfirmEmailView view from:
-    djang-allauth https://github.com/pennersr/django-allauth/blob/master/allauth/account/views.py#L190
+    djang-allauth https://github.com/pennersr/django-allauth/blob/master/allauth/account/views.py
 
+    Note: After 0.25.2 version django-allauth introduced a new pattern for account_confirm_email
+    .. code-block:: python
+        url(r'^account-confirm-email/(?P<key>[-:\w]+)/$', TemplateView.as_view(),
 
 2. I get an error: Reverse for 'password_reset_confirm' not found.
 

rest_auth/registration/urls.py

@@ -18,6 +18,6 @@ urlpatterns = [
     # If you don't want to use API on that step, then just use ConfirmEmailView
     # view from:
     # django-allauth https://github.com/pennersr/django-allauth/blob/master/allauth/account/views.py#L190
-    url(r'^account-confirm-email/(?P<key>\w+)/$', TemplateView.as_view(),
+    url(r'^account-confirm-email/(?P<key>[-:\w]+)/$', TemplateView.as_view(),
         name='account_confirm_email'),
 ]