Settings are always saved with command id #18111
Labels
Issue-Bug
It either shouldn't be doing this or needs an investigation.
Needs-Discussion
Something that requires a team discussion before we can proceed
Needs-Triage
It's a new issue that the core contributor team needs to triage at the next triage meeting
Windows Terminal version
1.21.2911.0
Windows build number
10.0.22631.4317
Other Software
No response
Steps to reproduce
Making any modification to the settings and saving them adds an
id
field to all actions.I don't use these IDs yet, and even when I do, then not for all of my actions.
This sounds harmless, but the annoying thing is related to #18110 -- I have a lot of
sendInput
actions (mapping obscure key combos to escape sequences which my environment knows about), and I'm forced to add useless IDs to all of them.Looks like they're optional -- BUT -- if I drop them, then next time Terminal rewrites my settings, it blesses me with a fresh layer of IDs, and I now need to check the differences and re-remove them. Since this is tedious and error prone, I'm effectively forced to accept this and add IDs. Life becomes unnecessarily more verbose with IDs that I'll never need.
Expected Behavior
No IDs added for actions unless I already had an id for them.
Actual Behavior
IDs are always added.
The text was updated successfully, but these errors were encountered: