Update send_verification_email and verify_email_and_activate #85
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.
I don't know if this function is already fix and I did not understand to use this framework well so, in my case, I have modified the
send_verification_email
function in thedjango-verify-email
package to allow sending verification emails directly using the user object when no form is provided. This enhancement is useful for projects using Django as the backend with a different framework, like React.I have also modified the
verify_user_and_activate
function that causes meNoReverseMatch
error when I don't have alogin_page
. The function has been modified to handle this issue that I encounter.Why This Contribution is Valuable:
This feature increases the flexibility of django-verify-email by allowing developers to use it in headless Django setups. It simplifies integration for projects using different frontend frameworks.
Thank you for considering my contribution. Please let me know if there are any changes or additional information needed.