Stefan Haller 19921b7c42 Fix json schema for context of CustomCommand ...

Previously the schema only allowed a single value; however, it is now possible
to specify multiple values separated by comma, and you would get very ugly red
error squiggles in VS Code when you did that.

The only solution that I can see is to get rid of the "enum" specification, and
mention the valid values only in the description. Add examples too so that you
get at least auto-completion.

2025-02-12 08:18:26 +01:00

..

app_config.go

Improve error reporting on config migration

2025-01-30 09:01:17 +01:00

config_default_platform.go

Change OpenCommand to Open and OpenLinkCommand to OpenLink

2023-04-13 13:14:00 +02:00

config_linux.go

Fix opening links containing ampersands (&) in WSL

2024-12-04 09:43:30 +01:00

config_windows.go

Change OpenCommand to Open and OpenLinkCommand to OpenLink

2023-04-13 13:14:00 +02:00

dummies.go

Make fields of AppConfig private

2024-08-18 10:24:52 +02:00

editor_presets_test.go

use 'suspend' instead of 'editInTerminal' internally

2023-08-09 22:03:58 +10:00

editor_presets.go

Fix micro editor preset

2025-01-09 08:48:59 +01:00

user_config_validation_test.go

UserConfig validation

2024-04-10 17:38:57 +02:00

user_config_validation.go

Revert "Add user config gui.commitAuthorFormat (#3625)"

2024-06-29 11:28:00 +02:00

user_config.go

Fix json schema for context of CustomCommand

2025-02-12 08:18:26 +01:00