-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Fix overriding preferences #5149
Conversation
const overriddeValue = preferenceValue[overriddenPreferenceName]; | ||
preferences[`${preferenceName}.${overriddenPreferenceName}`] = overriddeValue; | ||
const overriddenValue = preferenceValue[overriddenPreferenceName]; | ||
if (!preferences[`${preferenceName}`]) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
string interpolation is redundant then
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it breaks them, change editor.fontSize
for typescript
changes and observe that changes not auto applied to opened ts files. It works on master.
@akosyakov |
Signed-off-by: Anatoliy Bazko <abazko@redhat.com>
59d7e09
to
a235f1c
Compare
Signed-off-by: Anatoliy Bazko abazko@redhat.com
What does this PR do
It turns out that when we have overridden preferences in a configuration file
AbstractResourcePreferenceProvider
transforms it into"[xml].editor.autoClosingBrackets" : "never"
and it leads to that some extensions can't read these values.Debugging VS Code proved that it doesn't do this kind of transformation.
Reference issue
eclipse-che/che#12536