You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I searched existing issues and did not find a duplicate.
I am describing a concrete problem or use case, not just a vague idea.
Area
apps/web
Problem or use case
some old version of t3 code left behind conflicting keybinds. there is no way to reset keybinds to default from the GUI.
Proposed solution
A reset button next to each one would be nice, maybe along with a reset all button somewhere. If the reset button next to each keybind looks too cluttered, then maybe include it in the popup which appears when I click the keybind in the settings
Why this matters
Currently this breaks without a nice UX way to resolve it. I dont want to manually resolve keybind conflicts or throw my agent at some json to keep working keybinds
Smallest useful scope
add a reset all button
Alternatives considered
Actual migrations for the keybinds in the config file. If something has not been changed from the default by a user, then it should change automatically if the upstream default changes.
Risks or tradeoffs
migrations are more work to implement, ideally both a reset button and migrations would be there
Examples or references
look at how firefox about:config does this
makes messing with the config a whole lot less scary
Activity