-
-
Notifications
You must be signed in to change notification settings - Fork 7.5k
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
Finish renaming Display settings -> Preferences #26874
Comments
Hello @zulip/server-onboarding members, this issue was labeled with the "area: onboarding" label, so you may want to check it out! |
@zulipbot claim |
Welcome to Zulip, @Ciggzy1312! We just sent you an invite to collaborate on this repository at https://github.com/zulip/zulip/invitations. Please accept this invite in order to claim this issue and begin a fun, rewarding experience contributing to Zulip! Here's some tips to get you off to a good start:
As you work on this issue, you'll also want to refer to the Zulip code contribution guide, as well as the rest of the developer documentation on that site. See you on the other side (that is, the pull request side)! |
@zulipbot claim |
@arnavchhokra This issue cannot be claimed, as someone else is already working on it. Please see our contributor guide for advice on finding an issue to work on. Thanks! |
Fixes zulip#26874 Finish renaming 'display settings' -> 'preferences' in the following files zerver/lib/hotspots.py zerver/models.py Signed-off-by: Deepayan Mukherjee <deepayanmukherjee1312@gmail.com>
PR #26882 solves this issue |
Fixes zulip#26874 Finish renaming 'display settings' -> 'preferences'. Signed-off-by: Deepayan Mukherjee <deepayanmukherjee1312@gmail.com>
There's a lot more things that can be renamed.
If you choose to work on this further, please rename one element at a time -- e.g. |
is this issue still open to claim? |
@AdityaDKale yes, feel free to take it up |
@zulipbot claim |
@AdityaDKale No pressure, just curious if you're still working on this issue? |
Yes I am actually working on this issue. Thanks for concern. |
@zulipbot claim |
@ezekielmose This issue cannot be claimed, as someone else is already working on it. Please see our contributor guide for advice on finding an issue to work on. Thanks! |
I don't think I have to modify
according to your previous given answer @timabbott ? |
@ritikraj26 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! |
Working on it |
@zulipbot claim |
Welcome to Zulip, @Someone12543! We just sent you an invite to collaborate on this repository at https://github.com/zulip/zulip/invitations. Please accept this invite in order to claim this issue and begin a fun, rewarding experience contributing to Zulip! Here's some tips to get you off to a good start:
As you work on this issue, you'll also want to refer to the Zulip code contribution guide, as well as the rest of the developer documentation on that site. See you on the other side (that is, the pull request side)! |
Small update: still working on it! |
I have analyzed most of the instances that require changing, though a few questions have arisen... |
It'll be best to discuss in the Zulip development community for more visibility, thanks! |
Recently opened an aptly named topic in zulip's "issues" stream. |
I started by identifying the different types of "display_settings" and their references, all according to an earlier message in this issue (zulip#26874) from Tim Abbot. After analyzing the code for a solid few hours I determined that there were 3: a constant variable defined in server_events_dispatch.js; a few dictionaries in different files along with a filename; and a file named user_display_settings.hbs. Regarding this specific commit, I just had find all instances of the user_display_settings variable that wasn't the user_display_settings.hbs, and since all those instances were inside the web folder, I didn't have to worry about coupling issues, so all instances were simply changed to user_preferences.
@zulipbot abandon |
@zulipbot claim |
Hello @nimi11, it looks like you've currently claimed 1 issue in this repository. We encourage new contributors to focus their efforts on at most 1 issue at a time, so please complete your work on your other claimed issues before trying to claim this issue again. We look forward to your valuable contributions! |
@zulipbot claim |
Welcome to Zulip, @asttle! We just sent you an invite to collaborate on this repository at https://github.com/zulip/zulip/invitations. Please accept this invite in order to claim this issue and begin a fun, rewarding experience contributing to Zulip! Here's some tips to get you off to a good start:
As you work on this issue, you'll also want to refer to the Zulip code contribution guide, as well as the rest of the developer documentation on that site. See you on the other side (that is, the pull request side)! |
@zulipbot abandon |
@zulipbot claim |
Welcome to Zulip, @RitvikaSavanna! We just sent you an invite to collaborate on this repository at https://github.com/zulip/zulip/invitations. Please accept this invite in order to claim this issue and begin a fun, rewarding experience contributing to Zulip! Here's some tips to get you off to a good start:
As you work on this issue, you'll also want to refer to the Zulip code contribution guide, as well as the rest of the developer documentation on that site. See you on the other side (that is, the pull request side)! |
To finish out the work in #25945, we should update the following uses of "display settings" -> "preferences":
as well as many other variables in the code (#26874 (comment)):
CZO thread
The text was updated successfully, but these errors were encountered: