JSON schema of profiles.json doesn't accept "unbound" command of keybinding #6660

Closed
opened 2026-01-31 00:44:06 +00:00 by claunia · 4 comments
Owner

Originally created by @utgwkk on GitHub (Feb 29, 2020).

Originally assigned to: @zadjii-msft on GitHub.

According to Profiles.json Documentation, the following keybinding setting unbinds scrollUp from ctrl+shift+up and it actually unbinds the scrollUp command.

{
    "command": "unbound",
    "keys": ["ctrl+shift+up"]
},

But JSON schema validator raise warning to unbound with following message:

Incorrect type. Expected "object".

Originally created by @utgwkk on GitHub (Feb 29, 2020). Originally assigned to: @zadjii-msft on GitHub. <!-- Briefly describe which document needs to be corrected and why. --> According to [Profiles.json Documentation](https://github.com/microsoft/terminal/blob/master/doc/cascadia/SettingsSchema.md#keybindings), the following keybinding setting unbinds scrollUp from `ctrl+shift+up` and it actually unbinds the scrollUp command. ```json { "command": "unbound", "keys": ["ctrl+shift+up"] }, ``` But JSON schema validator raise warning to `unbound` with following message: >Incorrect type. Expected "object".
Author
Owner

@yozaam commented on GitHub (Mar 2, 2020):

Hey, I didn't find this in the docs are you talking of the lines,

unbound Unbind the associated keys from any command.
unbound Unbind the command.

Also maybe you're getting the warning because you put a comma at the end of your

{
    "command": "unbound",
    "keys": ["ctrl+shift+up"]
},

the " , " ?

@yozaam commented on GitHub (Mar 2, 2020): Hey, I didn't find this in the docs are you talking of the lines, unbound | Unbind the associated keys from any command. -- | -- unbound | Unbind the command. -- | -- Also maybe you're getting the warning because you put a comma at the end of your > > ```json > { > "command": "unbound", > "keys": ["ctrl+shift+up"] > }, > ``` > the " , " ?
Author
Owner

@DHowett-MSFT commented on GitHub (Mar 3, 2020):

Yeah, this should definitely work. We should also accept null, which I like rather more than "unbound".

@DHowett-MSFT commented on GitHub (Mar 3, 2020): Yeah, this should definitely work. We should also accept `null`, which I like rather more than `"unbound"`.
Author
Owner

@jelster commented on GitHub (Mar 18, 2020):

I think this issue might be more about handling of the "unbound" key binding, with the serialization error being what is expected when the extra , is included in the keymap array.

Yeah, this should definitely work. We should also accept null, which I like rather more than "unbound".

From what I can tell, #4988 demonstrates (ed: Resolves) this behavior

@jelster commented on GitHub (Mar 18, 2020): I think this issue might be more about handling of the "unbound" key binding, with the serialization error being what is expected when the extra `,` is included in the keymap array. > Yeah, this should definitely work. We should also accept `null`, which I like rather more than `"unbound"`. From what I can tell, #4988 demonstrates _(ed: Resolves)_ this behavior
Author
Owner

@musm commented on GitHub (Apr 2, 2020):

I'm also seeing the same

@musm commented on GitHub (Apr 2, 2020): I'm also seeing the same
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#6660