Skip to content

Should explicitly report the fatal settings error - #2451

Closed
snjeza wants to merge 1 commit into
redhat-developer:mainfrom
snjeza:issue-2429
Closed

Should explicitly report the fatal settings error#2451
snjeza wants to merge 1 commit into
redhat-developer:mainfrom
snjeza:issue-2429

Conversation

@snjeza

@snjeza snjeza commented May 13, 2022

Copy link
Copy Markdown
Collaborator

@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

@rgrunber rgrunber left a comment

Copy link
Copy Markdown
Member

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

snjeza commented May 26, 2022

Copy link
Copy Markdown
Collaborator Author

Is there a way to allow such cases for now ?

I will try.

@gorkem

gorkem commented Apr 7, 2026

Copy link
Copy Markdown
Contributor

@snjeza should this be closed?

@snjeza snjeza closed this Apr 7, 2026
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"

3 participants