feat: Optional Email Sterilization #14797
Open
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.
What?
A small but valuable change for people who need to encrypt data.
Why?
Currently there is no way (to mine and other's knowledge) to bypass the beforeChange hook for the email field within an auth collection. This makes it impossible for people to encrypt the field as it will lowercase and trim the encryption.
How?
Added
sterilize?: booleanto theEmailFieldtype so people can conditionally turn on and off the beforeChange hook that payload automatically injects into the email field.Pictures of changed code
The changes are very small so the files changed should be pretty clear, but here are some screenshots!
After of email field and hook:
After of the email field's type: