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

Refactor configuration entries #194

Closed
Confectrician opened this issue Jan 12, 2020 · 0 comments · Fixed by #247
Closed

Refactor configuration entries #194

Confectrician opened this issue Jan 12, 2020 · 0 comments · Fixed by #247
Labels
API-Breaking This will break the current structure and should be done during a major Version change enhancement
Milestone

Comments

@Confectrician
Copy link
Collaborator

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.

@Confectrician Confectrician added enhancement API-Breaking This will break the current structure and should be done during a major Version change labels Jan 12, 2020
@Confectrician Confectrician added this to the 1.0.0 milestone Jan 12, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
API-Breaking This will break the current structure and should be done during a major Version change enhancement
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant