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

Improve how settings are handled #11

Open
Nimaoth opened this issue Jun 29, 2024 · 0 comments
Open

Improve how settings are handled #11

Nimaoth opened this issue Jun 29, 2024 · 0 comments
Labels
enhancement New feature or request
Milestone

Comments

@Nimaoth
Copy link
Owner

Nimaoth commented Jun 29, 2024

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

@Nimaoth Nimaoth added the enhancement New feature or request label Jun 29, 2024
@Nimaoth Nimaoth added this to the Beta milestone Jun 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant