-
-
Notifications
You must be signed in to change notification settings - Fork 654
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
Do not show edit message option in message action sheet if edit time is passed or message edit is not allowed on that realm. #2792
Comments
Currently in zulip web app when edit/delete time limit exceeds, edit/delete option button is removed. Handle this feature in mobile version too, like this: 1.If it is "Private messages" narrow remove the buttons. 2.If it is "Topic or Stream messages" narrow keep edit button for editing of topic names, remove delete button. Fixes: zulip#2792,zulip#2793 Signed-off-by: rajprakash00 <rajprakash1999@gmail.com>
I believe there are two realm-specific server settings we'll need to read, in order to fix this issue:
So in particular we can't do something like assume message-editing is allowed and use a hard-coded time limit of 60 minutes, just because those are the settings on CZO. 🙂 |
Currently in zulip web app when edit/delete time limit exceeds, edit/delete option button is removed. Handle this feature in mobile version too, like this: 1.If it is "Private messages" narrow remove the buttons. 2.If it is "Topic or Stream messages" narrow keep edit button for editing of topic names, remove delete button. Fixes: zulip#2792,zulip#2793 Signed-off-by: rajprakash00 <rajprakash1999@gmail.com>
Handle the actual edit,delete message realm data as follows: * Import realm permission,timelimit data for edit,delete message into `realmReducer` from `initalDatatypes`.Handle types for them in `reduxTypes`. * Add all new realm data in `BackgroundData` in `MessageList`. * Handle the `backgroundData` params in `messageActionsheet`. * Add all the new realm data in `baseBackgroundData` in test files : `messageActionSheet-test`,`generateInboundEvents-test` and to `expectedState` in `realmReducer-test` file. Fixes: zulip#2792 Fixes: zulip#2793 Signed-off-by: rajprakash00 <rajprakash1999@gmail.com>
Handle the actual edit,delete message realm data as follows: * Import realm permission,timelimit data for edit,delete message into `realmReducer` from `initalDatatypes`.Handle types for them in `reduxTypes`. * Add all new realm data in `BackgroundData` in `MessageList`. * Handle the `backgroundData` params in `messageActionsheet`. * Add all the new realm data in `baseBackgroundData` in test files : `messageActionSheet-test`,`generateInboundEvents-test` and to `expectedState` in `realmReducer-test` file. Fixes: zulip#2792 Fixes: zulip#2793 Signed-off-by: rajprakash00 <rajprakash1999@gmail.com>
We've had another report of this; see https://chat.zulip.org/#narrow/stream/137-feedback/topic/checking.20edit.20time.20limit/near/1268322. See also #4615. |
It occurs to me that we also have to have some pretty subtle logic with some more inputs, like the user's role. Let's get #3898 done before this if we can. |
This will fix issues like
https://chat.zulip.org/#narrow/stream/48-mobile/topic/Inability.20to.20edit.20a.20message.20right.20after.20posting
@zulipbot claim
The text was updated successfully, but these errors were encountered: