--lsp option needs to support a connection id
chipsenkbeil opened this issue · comments
In the past, when using --lsp, we just needed to convert file://... into distant://... and vice versa. Now, our editor plugin supports multiple connections in the form of distant://{CONNECTION}@.... This means that when jumping to a definition or anything with a target, we're not including the connection, which can result in issues.
The solution is to let --lsp take an optional argument which is the prefix to use when translating file:// scheme.
Resolved by f2bd2f1
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.