Be more specific for pomade login errors #226

Closed
opened 2026-04-17 15:20:54 +00:00 by hodlbod · 4 comments
Owner

From #217

"Sorry, we were unable to log you in". That could be wrong password, wrong email, or a network issue. Users can't tell what to fix.

This can't entirely be fixed because part of the security model is not revealing registered emails, but we could change the error message to something like "Invalid login information" vs "Network error, please try again".

From #217 > "Sorry, we were unable to log you in". That could be wrong password, wrong email, or a network issue. Users can't tell what to fix. This can't entirely be fixed because part of the security model is not revealing registered emails, but we could change the error message to something like "Invalid login information" vs "Network error, please try again".
hodlbod added this to the Current milestone 2026-04-17 15:20:54 +00:00
hodlbod added the dev label 2026-04-17 15:20:54 +00:00
Collaborator

Hey @hodlbod, Would it be reasonable to address issues #226, #225, and #224 in a single PR?
I’d be interested in taking this on.

Hey @hodlbod, Would it be reasonable to address issues #226, #225, and #224 in a single PR? I’d be interested in taking this on.
userAdityaa was assigned by hodlbod 2026-04-17 18:33:34 +00:00
Author
Owner

Sure, go ahead.

Sure, go ahead.
Author
Owner

Well I guess the other issues have been assigned, so we can do it individually.

Well I guess the other issues have been assigned, so we can do it individually.
Collaborator

Closing this issue since the changes have been merged in PR #233.

Closing this issue since the changes have been merged in PR #233.
Sign in to join this conversation.
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: coracle/flotilla#226