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

Should explicitly report the fatal settings error #2451

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

snjeza
Copy link
Contributor

@snjeza snjeza commented May 13, 2022

@snjeza snjeza changed the title Should explicitly report the fatal settings error [WIP] Should explicitly report the fatal settings error May 13, 2022
Signed-off-by: Snjezana Peco <snjezana.peco@redhat.com>
@snjeza snjeza changed the title [WIP] Should explicitly report the fatal settings error Should explicitly report the fatal settings error May 13, 2022
Copy link
Member

@rgrunber rgrunber left a comment

Choose a reason for hiding this comment

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

Seems pretty reasonable, but things like :
~/Scripts/org.eclipse.jdt.core.prefs
${user.home}/Scripts/org.eclipse.jdt.core.prefs
are valid.

We did this using https://github.com/eclipse/eclipse.jdt.ls/blob/master/org.eclipse.jdt.ls.core/src/org/eclipse/jdt/ls/core/internal/ResourceUtils.java#L249 on the server side.

Is there a way to allow such cases for now ?

@snjeza
Copy link
Contributor Author

snjeza commented May 26, 2022

Is there a way to allow such cases for now ?

I will try.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Should explicitly report the fatal settings error like "URI is not hierarchical"
2 participants