Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

outboxActions: Show dialog if message send fails with informative ApiError #5878

Merged
merged 1 commit into from
Jul 10, 2024

Conversation

chrisbobbe
Copy link
Contributor

@chrisbobbe chrisbobbe commented Jul 10, 2024

outboxActions: Show dialog if message send fails with informative ApiError

This is our minimal support for #5870 in this legacy codebase.
Supporting it properly with a client-side check of the setting is
more effort than we can spare right now.

Probably more error handling is called for in general (like for
network or server issues), but #3881 ("Sending outbox messages is
fraught with issues") is complicated and it's probably best to leave
it be.

Fixes: #5870

@chrisbobbe chrisbobbe requested a review from gnprice July 10, 2024 02:57
@chrisbobbe
Copy link
Contributor Author

Screenshots from a dev server:

a b c
EF938FE1-8815-4B54-AB9A-45FB8294E8A9 BBA46F74-F912-492C-B47C-F2FD3B771839 99F52821-D8C8-4B5B-B4A1-AFFB4507798E

@alya
Copy link
Collaborator

alya commented Jul 10, 2024

Can we get a more accurate error in the non-authorized case? Like the webapp front end error:

image

Maybe this is something to fix on the server side?

@chrisbobbe
Copy link
Contributor Author

…Error

This is our minimal support for zulip#5870 in this legacy codebase.
Supporting it properly with a client-side check of the setting is
more effort than we can spare here, because it requires implementing
the group-based permissions system.

Probably more error handling is called for in general (like for
network or server issues), but zulip#3881 ("Sending outbox messages is
fraught with issues") is complicated and it's probably best to leave
it be.

Fixes: zulip#5870
@gnprice
Copy link
Member

gnprice commented Jul 10, 2024

Thanks! LGTM; merging.

Definitely would be good to fix that error message; we'll pursue doing so via that #api design thread.

I made one tweak to the commit message, elaborating on why we're not doing the full-featured version:

     This is our minimal support for #5870 in this legacy codebase.
     Supporting it properly with a client-side check of the setting is
-    more effort than we can spare right now.
+    more effort than we can spare here, because it requires implementing
+    the group-based permissions system.

@gnprice gnprice force-pushed the pr-send-message-api-error-dialog branch from a9208e5 to 2ae8d8e Compare July 10, 2024 22:51
@gnprice gnprice merged commit 2ae8d8e into zulip:main Jul 10, 2024
1 check passed
@chrisbobbe chrisbobbe deleted the pr-send-message-api-error-dialog branch July 10, 2024 22:52
@chrisbobbe
Copy link
Contributor Author

Makes sense; thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Support new settings for restricting direct messages
3 participants