You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Essentially it seems that user-specified sourcePaths are no longer used when resolving the filesystem path for a file in the stack trace after the above patch. The result is that we always return jdt:// paths which not all clients know how to handle.
It seems to me that we should always prefer filesystem paths (having applied user sourcePaths) over "internal" jdt:// paths.
The text was updated successfully, but these errors were encountered:
I submitted a detailed review on #354
Essentially it seems that user-specified
sourcePaths
are no longer used when resolving the filesystem path for a file in the stack trace after the above patch. The result is that we always returnjdt://
paths which not all clients know how to handle.It seems to me that we should always prefer filesystem paths (having applied user
sourcePaths
) over "internal"jdt://
paths.The text was updated successfully, but these errors were encountered: