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
It's then up to the LSP client to resolve the placeholder into the appropriate SObject names, field names, etc. for the users' current org.
This means any editor (besides VS Code) wanting to use the SOQL LSP server has to re-implement this placeholder resolution.
Describe the solution you'd like
Move the action of resolving placeholders from the LSP client into the LSP server.
Describe alternatives you've considered
The alternative is for each editor (client) to re-implement this functionality, which is counter to the point of having an LSP in the first place.
Additional context
I've successfully set up this language server using neovim as a client, but not being able to get completion for SObjects and fields limits its usefulness.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Currently, the SOQL language server produces various placeholders during completion:
It's then up to the LSP client to resolve the placeholder into the appropriate SObject names, field names, etc. for the users' current org.
This means any editor (besides VS Code) wanting to use the SOQL LSP server has to re-implement this placeholder resolution.
Describe the solution you'd like
Move the action of resolving placeholders from the LSP client into the LSP server.
Describe alternatives you've considered
The alternative is for each editor (client) to re-implement this functionality, which is counter to the point of having an LSP in the first place.
Additional context
I've successfully set up this language server using neovim as a client, but not being able to get completion for SObjects and fields limits its usefulness.
The text was updated successfully, but these errors were encountered: