-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Remove deserialization of legacy json keys #1069
Labels
Area-CodeHealth
Issues related to code cleanliness, linting, rules, warnings, errors, static analysis, etc.
Area-Settings
Issues related to settings and customizability, for console or terminal
Issue-Task
It's a feature request, but it doesn't really need a major design.
Needs-Tag-Fix
Doesn't match tag requirements
Priority-1
A description (P1)
Product-Terminal
The new Windows Terminal.
Resolution-Fix-Committed
Fix is checked in, but it might be 3-4 weeks until a release.
Milestone
Comments
zadjii-msft
added
Product-Terminal
The new Windows Terminal.
Issue-Task
It's a feature request, but it doesn't really need a major design.
Area-CodeHealth
Issues related to code cleanliness, linting, rules, warnings, errors, static analysis, etc.
labels
May 30, 2019
ghost
added
the
Needs-Triage
It's a new issue that the core contributor team needs to triage at the next triage meeting
label
May 30, 2019
DHowett-MSFT
added
Area-Settings
Issues related to settings and customizability, for console or terminal
and removed
Needs-Triage
It's a new issue that the core contributor team needs to triage at the next triage meeting
labels
May 30, 2019
No longer required. |
Hey so I'm re-activating this to make sure we pull the old keybindings that we're not going to support in >=1.0. These were changed in #3391 |
DHowett-MSFT
pushed a commit
that referenced
this issue
Jan 30, 2020
DHowett-MSFT
pushed a commit
that referenced
this issue
Jan 30, 2020
DHowett-MSFT
pushed a commit
that referenced
this issue
Jan 30, 2020
DHowett-MSFT
pushed a commit
that referenced
this issue
Jan 30, 2020
I've begun work on a bunch of facets of this (i guess as indicated by the commits above!) |
DHowett-MSFT
pushed a commit
that referenced
this issue
Mar 30, 2020
DHowett-MSFT
pushed a commit
that referenced
this issue
Mar 30, 2020
DHowett-MSFT
pushed a commit
that referenced
this issue
Mar 30, 2020
DHowett-MSFT
pushed a commit
that referenced
this issue
Mar 30, 2020
DHowett-MSFT
pushed a commit
that referenced
this issue
Mar 30, 2020
DHowett-MSFT
pushed a commit
that referenced
this issue
Mar 30, 2020
DHowett-MSFT
pushed a commit
that referenced
this issue
Mar 30, 2020
DHowett-MSFT
pushed a commit
that referenced
this issue
Mar 30, 2020
DHowett-MSFT
pushed a commit
that referenced
this issue
Mar 30, 2020
ghost
added
Resolution-Fix-Committed
Fix is checked in, but it might be 3-4 weeks until a release.
and removed
In-PR
This issue has a related PR
labels
Mar 31, 2020
DHowett-MSFT
pushed a commit
that referenced
this issue
Mar 31, 2020
🎉This issue was addressed in #5190, which has now been successfully released as Handy links: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Area-CodeHealth
Issues related to code cleanliness, linting, rules, warnings, errors, static analysis, etc.
Area-Settings
Issues related to settings and customizability, for console or terminal
Issue-Task
It's a feature request, but it doesn't really need a major design.
Needs-Tag-Fix
Doesn't match tag requirements
Priority-1
A description (P1)
Product-Terminal
The new Windows Terminal.
Resolution-Fix-Committed
Fix is checked in, but it might be 3-4 weeks until a release.
I'm thinking primarily of:
table
in a colorscheme as an array, not namescolorscheme
key (changed tocolorScheme
with "Color scheme" is two words #1054 )colorTable
(profile.colorTable
is broken #4091)The text was updated successfully, but these errors were encountered: