You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've looked around quite a bit, and from what I understand, the "Full Name" field on the email registration screen maps to displayName on the users collection. We want to skip collection of this field, or at least defer it until after the user is created. It seems like (though I'm not 100% certain, the docs are stingy on this) this field can be safely omitted from a user object, and we do not plan on using it in our apps directly.
What I'd like to see is a configuration option to skip collection of this field. The closest I can get right now is to simply hide that field by overriding the layout xml, which is hacky anyway, but that doesn't even really fix the problem that it is getting validated for presence by the UI in the email registration activity.
As of now, this field being required is a blocker. We would have to fork the repo or implement auth UI from scratch in order to get around this.
If there is a temporary work-around we can use, let me know.
Also I'm relatively new to firebase auth, so please let me know if I'm mistaken about any of this, or if you need more information.
The text was updated successfully, but these errors were encountered:
@tlubz as you said, you can safely omit this field from the Firebase Auth user object. I think this would be a good feature to add, the main concern with this and other enable/disable flags is how to expose them without adding an explosion of complexity/configuration to this library.
I've looked around quite a bit, and from what I understand, the "Full Name" field on the email registration screen maps to
displayName
on the users collection. We want to skip collection of this field, or at least defer it until after the user is created. It seems like (though I'm not 100% certain, the docs are stingy on this) this field can be safely omitted from a user object, and we do not plan on using it in our apps directly.What I'd like to see is a configuration option to skip collection of this field. The closest I can get right now is to simply hide that field by overriding the layout xml, which is hacky anyway, but that doesn't even really fix the problem that it is getting validated for presence by the UI in the email registration activity.
As of now, this field being required is a blocker. We would have to fork the repo or implement auth UI from scratch in order to get around this.
If there is a temporary work-around we can use, let me know.
Also I'm relatively new to firebase auth, so please let me know if I'm mistaken about any of this, or if you need more information.
The text was updated successfully, but these errors were encountered: