-
-
Notifications
You must be signed in to change notification settings - Fork 264
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
Handle user update events & consequential UI changes #988
Labels
area: event handling
How events from the server are responded to
GSoC
Possible GSoC project component
missing feature: user
A missing feature for all users, present in another Zulip client
Comments
15 tasks
To clarify for future readers, this is intended to track user information outside of presence data. |
6 tasks
mounilKshah
added a commit
to mounilKshah/zulip-terminal
that referenced
this issue
Aug 21, 2022
This commit contains new function called Model._handle_realm_user_events() which makes changes to the model.initial_data every time user metadata is changed. Partly fixes zulip#988.
mounilKshah
added a commit
to mounilKshah/zulip-terminal
that referenced
this issue
Aug 21, 2022
This commit contains new function called Model._handle_realm_user_events() which makes changes to the model.initial_data every time user metadata is changed. Partly fixes zulip#988.
4 tasks
@mounilKshah You have been unassigned from this issue because you have not made any updates for over 14 days. Please feel free to reclaim the issue if you decide to pick up again. Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area: event handling
How events from the server are responded to
GSoC
Possible GSoC project component
missing feature: user
A missing feature for all users, present in another Zulip client
Currently we regularly get new presence information, but I believe the user information is fixed as per the start of the session.
We should implement event handling to update the user data, as well as UI changes which may be necessary promptly, ie which aren't refreshed from the updated model data on a regular basis or as needed, though we could consider updating more frequently for better representation.
The text was updated successfully, but these errors were encountered: