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
Since the implementation of Custom Attrs, emails can also be saved to cryptopus. Custom Attrs currently uses the password before the email, that leads to this behavior
To me that doesn't really make sense, the email should be before the password, only problem then is that when you set username and email, the password wont be displayed in the row component.... since its only two fields per credential
In the show view, email is already displayed before the password.
I would recommend to include email before password everywhere, the current behavior could get really confusing, since most cryptopus users always expect the password to be on the right (2nd set attr)
Note:
While implementing custom attrs we already talked about this and the conclusion was that username/password are the two default attrs, that's why they are still the first two, before email :)
The text was updated successfully, but these errors were encountered:
Since the implementation of Custom Attrs, emails can also be saved to cryptopus. Custom Attrs currently uses the password before the email, that leads to this behavior
To me that doesn't really make sense, the email should be before the password, only problem then is that when you set username and email, the password wont be displayed in the row component.... since its only two fields per credential
In the show view, email is already displayed before the password.
I would recommend to include email before password everywhere, the current behavior could get really confusing, since most cryptopus users always expect the password to be on the right (2nd set attr)
Note:
While implementing custom attrs we already talked about this and the conclusion was that username/password are the two default attrs, that's why they are still the first two, before email :)
The text was updated successfully, but these errors were encountered: