Absytree
Absytree copied to clipboard
Improve how settings are handled
Currently settings are not declared anywhere, the code just uses them by specifying the name and a default value using
getOption[int](configProvider, "editor.max-search-results", 1000)
Problems:
- No place to put documentation for settings
- No easy way to get complete list of settings
- No auto completion/name checking when compiling
The new system should allow the following:
- Declare builtin settings in one place or multiple places but grouped by scope
- Specify documentation, type info etc. for each setting
- Allow plugins to declare their own settings
- Get compiler to check correct usages of builtin settings in compiler source and plugins
- Still allow accessing settings using string path
Once that is done a finder can be implemented similar to browse-keybinds to explore all available settings