Skip to content

Remove Base Layer from Settings UI#9655

Merged
2 commits merged intomainfrom
dev/cazamor/sui/remove-base-layer
Mar 30, 2021
Merged

Remove Base Layer from Settings UI#9655
2 commits merged intomainfrom
dev/cazamor/sui/remove-base-layer

Conversation

@carlos-zamora
Copy link
Member

Removes base layer (aka profiles.defaults) from the Settings UI. SettingContainer was also updated to not present a revert arrow when overriding a base layer value.

The new experience is now as follows:

  • The revert arrow will only appear if you are overriding a value from a fragment extension.
  • Users are still able to fully interact with profiles.defaults in their settings.json. Doing so still propagates those changes to their profiles as normal. In this case, the Settings UI presents the base layer value as the one that you selected.

#6800 - Settings UI Epic
Closes #9539

@carlos-zamora carlos-zamora requested a review from DHowett March 29, 2021 22:15
@ghost ghost added Area-SettingsUI Anything specific to the SUI Issue-Task It's a feature request, but it doesn't really need a major design. Priority-0 Bugs that we consider release-blocking/recall-class (P0) Product-Terminal The new Windows Terminal. labels Mar 29, 2021
Copy link
Member

@DHowett DHowett left a comment

Choose a reason for hiding this comment

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

Okay. We can revert this or look at the original code when we want to bring it back. Which we will.

@DHowett DHowett added zPreview-Service-Consider AutoMerge Marked for automatic merge by the bot when requirements are met labels Mar 30, 2021
@ghost
Copy link

ghost commented Mar 30, 2021

Hello @DHowett!

Because this pull request has the AutoMerge label, I will be glad to assist with helping to merge this pull request once all check-in policies pass.

p.s. you can customize the way I help with merging this pull request, such as holding this pull request until a specific person approves. Simply @mention me (@msftbot) and give me an instruction to get started! Learn more here.

@ghost ghost merged commit 19fb9b2 into main Mar 30, 2021
@DHowett
Copy link
Member

DHowett commented Mar 30, 2021

I am glad that this will conflict with 1.7 because of the xaml reformatting -.-

@ghost ghost deleted the dev/cazamor/sui/remove-base-layer branch March 30, 2021 15:15
DHowett pushed a commit that referenced this pull request Apr 2, 2021
Removes base layer (aka profiles.defaults) from the Settings UI. `SettingContainer` was also updated to not present a revert arrow when overriding a base layer value.

The new experience is now as follows:
- The revert arrow will only appear if you are overriding a value from a fragment extension.
- Users are still able to fully interact with `profiles.defaults` in their settings.json. Doing so still propagates those changes to their profiles as normal. In this case, the Settings UI presents the base layer value as the one that you selected.

Closes #9539

(cherry picked from commit 19fb9b2)
@ghost
Copy link

ghost commented Apr 14, 2021

🎉Windows Terminal v1.7.1033.0 has been released which incorporates this pull request.:tada:

Handy links:

@ghost ghost mentioned this pull request Apr 14, 2021
@ghost
Copy link

ghost commented Apr 14, 2021

🎉Windows Terminal Preview v1.8.1032.0 has been released which incorporates this pull request.:tada:

Handy links:

DHowett added a commit that referenced this pull request Jul 1, 2021
This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Area-SettingsUI Anything specific to the SUI AutoMerge Marked for automatic merge by the bot when requirements are met Issue-Task It's a feature request, but it doesn't really need a major design. Priority-0 Bugs that we consider release-blocking/recall-class (P0) Product-Terminal The new Windows Terminal.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Remove base layer from settings UI

3 participants