Skip to content

Add expander groups to settings UI#20200

Draft
carlos-zamora wants to merge 2 commits intomainfrom
dev/cazamor/sui-rejuv/expander-groups
Draft

Add expander groups to settings UI#20200
carlos-zamora wants to merge 2 commits intomainfrom
dev/cazamor/sui-rejuv/expander-groups

Conversation

@carlos-zamora
Copy link
Copy Markdown
Member

Summary of the Pull Request

Adds expander groups throughout the entire settings UI to group similar settings together.

There are also a few minor changes that were folded into this PR:

  • "Appearance" page was renamed to "Personalization"
  • Move settings from "Rendering" page to "Compatibility"

Those were done as a part of this PR for a holistic restructuring. Given that spacing has changed, the content also needs to be reviewed so that it looks right with this new structure (i.e. long help text should be reconsidered to be shorter).

Validation Steps Performed

Scenarios:

  • ensure all settings are in expanders
    • Startup
    • Interaction
    • Personalization
    • Color schemes
    • Compatibility
    • Profile page
  • settings search still works and deep links

PR Checklist

Related to #17000

<TextBox Style="{StaticResource TextBoxSettingStyle}"
Text="{x:Bind Profile.TabTitle, Mode=TwoWay}" />
</local:SettingContainer>
<!-- Section: Visual/UI Affordance -->
<comment>Description for the "Rendering" section.</comment>
</data>
<data name="Profile_Section_VisualUI_Title.Text" xml:space="preserve">
<value>Visual/UI Affordance</value>
GETSET_BINDABLE_ENUM_SETTING(TextMeasurement, winrt::Microsoft::Terminal::Control::TextMeasurement, _settings.GlobalSettings().TextMeasurement);
GETSET_BINDABLE_ENUM_SETTING(AmbiguousWidth, winrt::Microsoft::Terminal::Control::AmbiguousWidth, _settings.GlobalSettings().AmbiguousWidth);

// Settings merged in from the former RenderingViewModel.
Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Whoops. Needs to be removed.

@github-actions
Copy link
Copy Markdown

github-actions Bot commented May 8, 2026

@check-spelling-bot Report

⚠️ Dictionary not found

Problems were encountered retrieving check dictionaries (cspell:cpp/src/stdlib-cpp.txt cspell:dart/src/dart.txt cspell:cpp/src/ecosystem.txt cspell:cpp/src/compiler-gcc.txt cspell:latex/dict/latex.txt cspell:python/src/python/python.txt cspell:java/src/java.txt cspell:haskell/dict/haskell.txt cspell:python/src/python/python-lib.txt cspell:cpp/src/lang-jargon.txt cspell:cpp/src/compiler-msvc.txt cspell:cpp/src/lang-keywords.txt cspell:cpp/src/compiler-clang-attributes.txt cspell:java/src/java-terms.txt cspell:ruby/dict/ruby.txt cspell:public-licenses/src/additional-licenses.txt cspell:ada/dict/ada.txt cspell:r/src/r.txt cspell:cpp/src/stdlib-cerrno.txt cspell:software-terms/dict/webServices.txt cspell:dotnet/dict/dotnet.txt cspell:k8s/dict/k8s.txt cspell:sql/src/tsql.txt cspell:css/dict/css.txt cspell:cpp/src/stdlib-c.txt cspell:python/src/common/extra.txt cspell:npm/dict/npm.txt cspell:node/dict/node.txt cspell:shell/dict/shell-all-words.txt cspell:cpp/src/template-strings.txt cspell:golang/dict/go.txt cspell:php/dict/php.txt cspell:gaming-terms/dict/gaming-terms.txt cspell:software-terms/dict/softwareTerms.txt cspell:cpp/src/stdlib-cmath.txt cspell:cpp/src/people.txt cspell:elixir/dict/elixir.txt cspell:swift/src/swift.txt cspell:fullstack/dict/fullstack.txt cspell:clojure/src/clojure.txt cspell:powershell/dict/powershell.txt cspell:scala/dict/scala.txt cspell:svelte/dict/svelte.txt cspell:rust/dict/rust.txt cspell:docker/src/docker-words.txt cspell:lua/dict/lua.txt cspell:public-licenses/src/generated/public-licenses.txt cspell:typescript/dict/typescript.txt cspell:redis/dict/redis.txt cspell:monkeyc/src/monkeyc_keywords.txt cspell:django/dict/django.txt cspell:html/dict/html.txt cspell:python/src/additional_words.txt cspell:sql/src/sql.txt).

⚠️ For more information, see check-dictionary-not-found.

🔴 Please review

See the 📂 files view, the 📜action log, 👼 SARIF report, or 📝 job summary for details.

Unrecognized words (1)

Affordance

These words are not needed and should be removed notif

To accept these unrecognized words as correct and remove the previously acknowledged and now absent words, you could run the following commands

... in a clone of the git@github.com:microsoft/terminal.git repository
on the dev/cazamor/sui-rejuv/expander-groups branch (ℹ️ how do I use this?):

curl -s -S -L 'https://raw.githubusercontent.com/check-spelling/check-spelling/cfb6f7e75bbfc89c71eaa30366d0c166f1bd9c8c/apply.pl' |
perl - 'https://github.com/microsoft/terminal/actions/runs/25533297185/attempts/1' &&
git commit -m 'Update check-spelling metadata'
Available 📚 dictionaries could cover words (expected and unrecognized) not in the 📘 dictionary

This includes both expected items (2012) from .github/actions/spelling/expect/alphabet.txt .github/actions/spelling/expect/expect.txt .github/actions/spelling/expect/web.txt and unrecognized words (1)

Dictionary Entries Covers Uniquely
cspell:csharp/csharp.txt 32 2 2
cspell:aws/aws.txt 232 2 2
cspell:fonts/fonts.txt 536 1 1

Consider adding to the extra_dictionaries array (in the .github/actions/spelling/config.json file):

    "cspell:csharp/csharp.txt",
    "cspell:aws/aws.txt",
    "cspell:fonts/fonts.txt",

To stop checking additional dictionaries, put (in the .github/actions/spelling/config.json file):

"check_extra_dictionaries": []
Warnings ⚠️ (1)

See the 📂 files view, the 📜action log, 👼 SARIF report, or 📝 job summary for details.

⚠️ Warnings Count
⚠️ check-dictionary-not-found 54

See ⚠️ Event descriptions for more information.

✏️ Contributor please read this

By default the command suggestion will generate a file named based on your commit. That's generally ok as long as you add the file to your commit. Someone can reorganize it later.

If the listed items are:

  • ... misspelled, then please correct them instead of using the command.
  • ... names, please add them to .github/actions/spelling/allow/names.txt.
  • ... APIs, you can add them to a file in .github/actions/spelling/allow/.
  • ... just things you're using, please add them to an appropriate file in .github/actions/spelling/expect/.
  • ... tokens you only need in one place and shouldn't generally be used, you can add an item in an appropriate file in .github/actions/spelling/patterns/.

See the README.md in each directory for more information.

🔬 You can test your commits without appending to a PR by creating a new branch with that extra change and pushing it to your fork. The check-spelling action will run in response to your push -- it doesn't require an open pull request. By using such a branch, you can limit the number of typos your peers see you make. 😉

If the flagged items are 🤯 false positives

If items relate to a ...

  • binary file (or some other file you wouldn't want to check at all).

    Please add a file path to the excludes.txt file matching the containing file.

    File paths are Perl 5 Regular Expressions - you can test yours before committing to verify it will match your files.

    ^ refers to the file's path from the root of the repository, so ^README\.md$ would exclude README.md (on whichever branch you're using).

  • well-formed pattern.

    If you can write a pattern that would match it,
    try adding it to the patterns.txt file.

    Patterns are Perl 5 Regular Expressions - you can test yours before committing to verify it will match your lines.

    Note that patterns can't match multiline strings.

@carlos-zamora
Copy link
Copy Markdown
Member Author

Demos

image image image image image image image image

TODO

  • Profile > Appearance: "Transparency" and "Window" should probably be a group(?) or folded into something
  • Profile > Appearance: Consider doing something about "Unfocused appearance" (UI doesn't fit in as well imo)
  • Profile > Terminal Emulation: do we want some groupings here? (leaning no)
  • Profile > Advanced: do we want some groupings here? (leaning yes)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants