Skip to content
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

Settings are always saved with command id #18111

Open
ebarzilay-godaddy opened this issue Oct 26, 2024 · 0 comments
Open

Settings are always saved with command id #18111

ebarzilay-godaddy opened this issue Oct 26, 2024 · 0 comments
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

Comments

@ebarzilay-godaddy
Copy link

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.

@ebarzilay-godaddy ebarzilay-godaddy added Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels Oct 26, 2024
@carlos-zamora carlos-zamora added the Needs-Discussion Something that requires a team discussion before we can proceed label Oct 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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
Projects
None yet
Development

No branches or pull requests

2 participants