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

8349-support-vscode-settings-schemas #8761

Merged

Conversation

danarad05
Copy link
Contributor

@danarad05 danarad05 commented Nov 18, 2020

Signed-off-by: Dan Arad dan.arad@sap.com

What it does

fixes: #8349 #8673

How to test

Open a workspace and check if there are warnings concerning "vscode://schemas/settings/folder" schema.
image

Review checklist

Reminder for reviewers

@danarad05
Copy link
Contributor Author

@akosyakov @vince-fugnitto
cc: @amiramw
In regards to issue #8349:

  1. I have added registration of workspaceSchema and folderSchema uri (user,launch, task exist already). Is that what you meant in 8349?
  2. Also there are some other scopes - 'application' | 'machine' | 'window' | 'resource' | 'language-overridable' | 'machine-overridable' which I'm not sure if should be added.
  3. Also, Should I update code using getCombinedSchema()?
  • for instance generateTree() in preference-tree-generator.ts has entire logic for building pref tree based on combinedSchema.
  • also updateUnderlyingData in preference-tree-provider.ts is based on combinedSchema for hiding/showing properties for preferences pages.

Thanks

@danarad05 danarad05 force-pushed the 8349-support-vscode-settings-schemas branch from 6032007 to 71c2b7c Compare December 2, 2020 10:26
@amiramw
Copy link
Member

amiramw commented Dec 10, 2020

  1. I have added registration of workspaceSchema and folderSchema uri (user,launch, task exist already). Is that what you meant in 8349?

I think it is good enough scope for this PR. Not sure about 8349. There can be future work done on preference UI like vscode that shows all folders in workspace and their specific preferences.

  1. Also there are some other scopes - 'application' | 'machine' | 'window' | 'resource' | 'language-overridable' | 'machine-overridable' which I'm not sure if should be added.

Maybe le'ts keep it workspace and folder for now.

How to test
TBD

There should one less warning on problem view about missing schema for folder.

… folder schema uris

Signed-off-by: Dan Arad <dan.arad@sap.com>
@danarad05 danarad05 force-pushed the 8349-support-vscode-settings-schemas branch from 762873e to bd57b03 Compare December 13, 2020 09:36
@danarad05
Copy link
Contributor Author

danarad05 commented Dec 13, 2020

@amiramw see my comments - updated. Please review again.
Thanks

Also, please rerun again second build (Error: The process '/usr/bin/xvfb-run' failed with exit code 1) Thanks.

@amiramw
Copy link
Member

amiramw commented Dec 13, 2020

@danarad05 i see now that the warning about folder scehma is gone. However there are more warnings now than before for some reason. Please check.
Before:
image
Now:
image

@danarad05
Copy link
Contributor Author

@amiramw

@danarad05 i see now that the warning about folder scehma is gone. However there are more warnings now than before for some reason. Please check.

After "vscode://schemas/settings/folder" is now fixed, builtin extension "vscode.json-language-features" is now able to load it's contents and run validation on it.
image

image

image

image

Copy link
Member

@amiramw amiramw left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For the scope of eliminating constant problem about missing schema and for showing extra warnings coming from settings folder schema this PR is good enough and seems to work fine.

There is additional work for embedding it in preference UI etc. (like in vs code). But it can be done later IMO.

@amiramw amiramw merged commit 7e8992b into eclipse-theia:master Jan 11, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

support vscode settings schemas
2 participants