Describe the solution you'd like
We should refactor our configuration entries to add some hierarchy and clarifications.
This way we can structure the config in a more logical way and also make some thigns clearer for users.
Example:
Currently the auth config parameters lead to confusion sometimes and people try to fill them with console credentials or pi credentials.
We can try to improve this by presenting them in a special basic auth category.
Same goes for LSP related settings.
Describe alternatives you've considered
None.
Additional context
Configuration changes will lead to some problems, caused by cached addon data.
(Especially when settings moved or have gone, which will be the case here.)
So this is api breaking for me and considered to be implemented in the next major version.
Is your feature request related to a problem? Please describe. According to https://code.visualstudio.com/api/references/contribution-points#contributes.configuration one can change the presentation of an extensions configuration with the way how configuration entries are made.
Describe the solution you'd like We should refactor our configuration entries to add some hierarchy and clarifications. This way we can structure the config in a more logical way and also make some thigns clearer for users.
Example: Currently the auth config parameters lead to confusion sometimes and people try to fill them with console credentials or pi credentials. We can try to improve this by presenting them in a special basic auth category.
Same goes for LSP related settings.
Describe alternatives you've considered None.
Additional context Configuration changes will lead to some problems, caused by cached addon data. (Especially when settings moved or have gone, which will be the case here.) So this is api breaking for me and considered to be implemented in the next major version.