fix(authentication-local): Local Auth - Nested username & Password fields #3091
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.
In my application, I store all the authentication related information related to the user in a nested object. This nested subobject includes for example, the last login time, the password hash & salt, last login IP address etc and in my case it is called
_auth
. The problem is that currently the library only allows you to confirgure the username and password fields for authentication to only be on the top level of the entity.A test has been added for the nested field case and lint rules passing locally.
Summary
(If you have not already please refer to the contributing guideline as described
here)
If so, please mention them to keep the conversations linked together.