Skip to content
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

LSP and future plans for this extension. #95

Open
panoply opened this issue Oct 27, 2021 · 1 comment
Open

LSP and future plans for this extension. #95

panoply opened this issue Oct 27, 2021 · 1 comment

Comments

@panoply
Copy link

panoply commented Oct 27, 2021

Hello,

Thanks for making this tool available for those of us taking advantage of FaunaDB.

As of right now, this extension is not using LSP. In order to provide features like completions and/or potentially diagnostics, it would be a good decision to leverage LSP. I don't know whether the Fauna team has thought about the approach they will take but to facilitate modern IDE capabilities when working with .fql files some consideration could be taken on this topic. While totally possible to achieve on the client when it comes to language features per-say reaching for the protocol is a better fit, whereas the client is perfect for UX additions in the editor, the server enriches the language aspects.

Considering the structure of how we express FQL queries and in order to provide intelliSense capabilities like completions, signatures, validations/diagnostics and in addition formatting (with rulesets) via LSP then.fql files would require parsing and as such some lexical analysis. I would be happy to write a scanner/parser for such a case in order to facilitate those capabilities but to embark upon this will likely involve an overhaul of the current structure (ie: moving some of the logic to the server) as the protocol can handle so much more than the client. Such a task is not taken on without consideration and it takes time, it cannot be hacked up in a couple days, so can I get some clarification on the following:

  1. Do this extension maintainers have plans for LSP?
  2. If yes, are there plans for appropriating a scanner/parser?
  3. What features have the team considered for the FQL extension, ie: signatures/diagnostics etc?
  4. Are there plans for cross-editor support? ie: sublime, atom etc etc.

FQL has the potential to really make an impact on the development community and in addition solidify itself as a top player across the nexus but editor capabilities that provide features developers have become so accustomed does somewhat border necessity nowadays. I really love leveraging FQL and while GQL is awesome and holds the monopoly I truly believe in the power of FQL over Graph. As such, I would love to see it become more renowned but without the IDE foundations, developers will be less inclined to make it apart of their stack.

Thank you for your time.

@panoply
Copy link
Author

panoply commented Nov 24, 2021

Bumping this as no response in a month. Clarification would be nice.

Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant