Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Separate runtime TerminalSettings from profile-TerminalSettings #8602
Separate runtime TerminalSettings from profile-TerminalSettings #8602
Changes from 7 commits
8b64425
403646f
7b5e04e
21139f5
7079e60
1fc3e8b
5151a7f
8d2c583
a288001
ceb1d00
b57ee23
ab36124
b9ef9f1
54e5123
8d27531
efd9176
b29183f
8cb6501
f402a8c
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
(This is a much larger discussion that doesn't have to be implemented as a part of this PR. So really I'm thinking out loud.)
I'm wondering if we should move
TerminalSettings
over to TerminalSettingsModel. Hear me out:TerminalSettings
IInheritable
, might as well moveTerminalSettings
over to TSM. It's a bit weird for us to grab this random file from a separate project, right? hahaTerminalSettings
by firing an event to TermApp, but then TermApp would need to somehow get the synthesizedTerminalSettings
object down to the profile page and update on each change. HavingTerminalSettings
be its own project or a part of TSM makes it it so much easier to constructTerminalSettings
and just have one readily available for a TermControl preview.What do you think?
CC @DHowett for thoughts on this matter too. I might just be approaching the two things above completely wrong haha
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.
You might have a point here (but it should probably be a follow up)
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.
Bumping this thread for @DHowett because this is important for the terminal preview in SUI.
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.
(Chatted in meeting.)