Skip to content

Add check for relative paths#704

Merged
davidanthoff merged 1 commit intomasterfrom
path-diagnostic
May 18, 2020
Merged

Add check for relative paths#704
davidanthoff merged 1 commit intomasterfrom
path-diagnostic

Conversation

@davidanthoff
Copy link
Copy Markdown
Member

Helps diagnose #703.

The general idea is that we want to figure out where relative paths come from, and this might help us to narrow that scenario down. My understanding is that we will never receive a URI from a client with a relative path, but that those relative paths originate somewhere in our own code, maybe in the include following logic of StaticLint? Of course, I would just generally remove any loading of non-workspace files from disc :)

CC @pxl-th and @non-Jedi.

@davidanthoff davidanthoff added this to the Current milestone May 17, 2020
@davidanthoff davidanthoff requested a review from ZacLN May 17, 2020 19:47
@ZacLN
Copy link
Copy Markdown
Contributor

ZacLN commented May 17, 2020

It's almost certainly coming from within StaticLint but this isn't related to whether a file is in the workspace or not. I don't think this PR would give us the info we need (it'll notify of the issue but not how it's come about), I'll make one for SL

@davidanthoff
Copy link
Copy Markdown
Member Author

We should probably still merge this, right? It can't harm and essentially would make sure we would notice any problem in this area.

@davidanthoff davidanthoff merged commit ccc4813 into master May 18, 2020
@davidanthoff davidanthoff deleted the path-diagnostic branch May 18, 2020 19:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants