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
Invite.js's multiinvite stuff builds up a nice list of error reasons, which are then lost by the time they're displayed in _showAnyInviteErrors in ChatInviteDialog.js
The text was updated successfully, but these errors were encountered:
ara4n
added
T-Defect
S-Major
Severely degrades major functionality or product features, with no satisfactory workaround
P2
ui/ux
S-Tolerable
Low/no impact on users
and removed
S-Major
Severely degrades major functionality or product features, with no satisfactory workaround
labels
Feb 21, 2017
Fixeselement-hq/element-web#3283Fixeselement-hq/element-web#3968Fixeselement-hq/element-web#4308Fixeselement-hq/element-web#1597Fixeselement-hq/element-web#6790
This does 3 things:
* Makes the `MultiInviter` check for a user profile before attempting an invite. This is to prove the user exists.
* Use the `MultiInviter` everywhere to avoid duplicating the logic. Although a couple places only invite one user, it is still worthwhile.
* Communicate errors from the `MultiInviter` to the user in all cases. This is done through dialogs, where some existed previously but were not invoked.
Specifically to the 403 error not working: What was happening was the `MultiInviter` loop was setting the `fatal` flag, but that didn't resolve the promise it stored. This caused a promise to always be open, therefore never hitting a dialog.
Invite.js's multiinvite stuff builds up a nice list of error reasons, which are then lost by the time they're displayed in _showAnyInviteErrors in ChatInviteDialog.js
The text was updated successfully, but these errors were encountered: