-
Notifications
You must be signed in to change notification settings - Fork 4k
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
LSIF tool has uncaught exception when Uri is relative path #59692
Comments
@noellelc Hmm, so for source generated files where we don't have a full path, what would you like us to do? I can do |
We correctly handled them in the core generation code, but failed as we were actually serializing out JSON. Fixes dotnet#59692
It looks like in your PR @jasonmalinowski you're just going to leave it as a relative path, which works for us! |
@noellelc All right, we'll go with that for now! |
@noellelc And I guess to clarify it's just a relative path. Not even a file:// prefix; that OK? |
Yes--we have checks that allow for a relative uri. Thanks! |
Version Used: 4.0.0-3.21372.2
Steps to Reproduce:
Expected Behavior:
Tool still runs sucessfully if document uris are relative paths.
Actual Behavior:
I'm not sure if this is the root cause, but it appears at this point in the Generator tool, a relative or absolute uri is expected for document, but here, an absolute uri is expected but uncaught if the uri is not absolute.
The text was updated successfully, but these errors were encountered: