-
Notifications
You must be signed in to change notification settings - Fork 4k
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
Rename "Options" modal to "Preferences". #25683
Conversation
Size Change: +18 B (0%) Total Size: 1.18 MB
ℹ️ View Unchanged
|
1d0e13a
to
7d49d7c
Compare
Hello, Carolyn from editorial. I agree that "preferences" works better than "options". Is there anything else you would like me to look at? |
There's no other copy changes in this PR besides the renaming, so that's all. Thank you for your quick review! 😄 |
7d49d7c
to
11f6ea8
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
25 changed files just to change a string. There must be something wrong! 😆
Jokes apart, makes sense to me. Quick question:
Should the "Keyboard options" section within the modal be renamed to "Keyboard preferences"? Or maybe just remove the word "options" as it seems to me this is the only section name with the term "options", not sure why.
From a technical perspective, I don't have the knowledge to determine whether these changes need deprecations/aliases or whatever, given fome files and components are renamed.
@afercia To be fair, I'm changing the CSS class names and function names, which isn't strictly necessary, but the confusion between the "More options" button and "Options" modal applies to the internal names as well, so I figured I ought to change them too. And of course, I had to update all the unit tests and end-to-end tests that check for specific classes and strings. I'm pretty sure most of the internal name changes should be fine. The only thing I'm not sure about is changing And yeah, "Keyboard options" should probably just be "Keyboard", though I figure that should be its own PR. |
@ZebulanStanphill sure, I was joking on the changed files number, mostly because I'm surprised that in "modern development" one has to change 25 files to rename a string to "do it right". Old-school guy here, missing the old good days when changing a string was just... changing a string 🙂
I'd say: throw that change in and pretend others don't see it |
Now that I think about it, the Preferences modal probably shouldn't even have its own CSS class. I see it uses it for section margins... but I think that kind of styling should probably be made generic to all modals. Of course, the Preferences modal is likely to be completely redesigned soon, so I guess we can probably remove the class along the way when we implement that. |
I'm fine with this change, don't have a strong opinion but seems "Preferences" can be a better fit. Also happy with sneaking in "Keyboard options" → "Keyboard" :) |
I'm going to remove the design feedback as for me I'm also keen on not having options > options. I'd +1 the change @mtias suggests of using this as an option to remove other 'options'. I do think it could do with a little code check as that feels like quite a lot of spots it's in, as has been noted this could be a great opportunity for iteration there and streaming of process. |
11f6ea8
to
d62ba6b
Compare
Applied the "Keyboard options" to "Keyboard" change. |
d62ba6b
to
cea3af6
Compare
cea3af6
to
87c6117
Compare
87c6117
to
b93b480
Compare
I'm going to go ahead and merge this. |
Description
This PR renames the "Options" modal to "Preferences". This helps get rid of the confusion of having an "Options" option located under the "Options" menu. (See, it even sounds confusing! 😛) This also helps narrow down the purpose of the modal a bit, and makes it clear what kind of options belong in it.
There are no functional changes in this PR. Only name changes.
Screenshots
Before
After
Checklist: