[ENH] Improving activating whitelist support for Java DSL about camel-lsp-client-vscode HOT 3 CLOSED

I don't think that camel keyword is a big requirements as it will be part of import package for RouteBuilder which will be a very common use case to have in the file.

I would like to avoid to have something specific to users to specify when to activate it in client side or not and have a smarter detection on Language server side.
Having it on client side means that we will need to develop it X times, X being the number of IDE clients (currently 3).

For smarter detection:

• other heuristics?
• see if Camel built-in parsers can be used
• see if we put a dependency on jdt.ls and reuse the classpath mechanism available so that we can detect the exact correct class available.

The goal was to release a first version with some constraints and see the feedback from users if we really need to go further or not, and with which priority.

from camel-lsp-client-vscode.

Ah, sorry, I had misread the article and thought that camel was a requirement in the file name, not just to be present in the content of the file.

That was probably the main point in my enhancement request, so since it was never valid, we can even ignore this request.

I'd personally like the idea to be able to have the support also for an in-progress no name file, but that's not super important.

from camel-lsp-client-vscode.

to have the support also for an in-progress no name file

I don't think that a lot of IDEs are able to provide great support on non-named file; I just tried with VS Code and there is not even syntax coloring for Java. On Eclipse Desktop, you are forced to provide a name first.

from camel-lsp-client-vscode.