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)
[X] Tell us about the problem your pull request is solving. Please see above
[X] Are there any open issues that are related to this? No
[X] Is this PR dependent on PRs in other repos? No
If so, please mention them to keep the conversations linked together.
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.