camel-tooling / camel-lsp-client-vscode Goto Github PK

View Code? Open in Web Editor NEW

24.0 24.0 13.0 50.72 MB

This is a client implementation of the Apache Camel Language Server Protocol for Visual Studio Code

License: Apache License 2.0

JavaScript 0.44% TypeScript 98.33% Java 1.07% Groovy 0.04% Kotlin 0.12%

apache-camel camel lsp vscode vscode-extension vscode-language

camel-lsp-client-vscode's People

Contributors

Stargazers

Watchers

Forkers

lhein apupier dgolovin djelinek srsharon melissaflinn mlorinc benoitf unsortedhashsets joshiraez sureshchandra999 pospisilf hdamarcelo

camel-lsp-client-vscode's Issues

Fix display of readme for second-level indentation

Suggestion: detail current features

Hi, I have installed vscode plugin but I'm struggling to understand what features the plugin has and where I should see its behavior kicking in.

I would like to read a more explicit list of currently supported features. For example:

which DSL are supported? (java/xml/blueprint/whatever)
does the autocompletion kick in while I'm editing an endpoint URI ?
anything else?

A quick video might be good to show case the features, but personally I'd like to see these feature in form of a quick cropped screenshot that can give me, with a glimpse of an eye, all the information that I need.

thank you

Launch test with java 11 and Java 17 on CI

Prepare automated tests for Camel LSP for VS Code

Use Maven artefact instead of github artefact for the server

Log file of the plugin is created in the "opened folder" of VS Code

Download server dependency from Maven instead of github

Update to name given by legal department

add "by Red Hat"

download of the server jar fails with 404

Causes add comment to use java comment instead of xml comment tag

When enabling this plugin the add comment function in vscode adds // instead of an xml comment tag to xml files.

Update Travis build due to API break with xfvb

0.00s$ sh -e /etc/init.d/xvfb start
sh: 0: Can't open /etc/init.d/xvfb
The command "sh -e /etc/init.d/xvfb start" failed and exited with 127 during .

https://benlimmer.com/2019/01/14/travis-ci-xvfb/

Provide better naming in outline when several Language servers are activated

when using the xml language server, the outline has 2 providers. it seems that the extension name is used by default which is nto very nice for us as it is too long

it would be better to be able to display only "Apache Camel" or "Camel" or "Camel structure"

Clear message "starting apache camel language server" when the server is started

Provide insert-and-replace changelog entry

camel-tooling/camel-language-server#55

Add bump to Camel 2.24.2 in changelog

automatic pr merged on server side camel-tooling/camel-language-server#295

[Regression]Diagnostics for Camel URIs is not working

Environment

latest build of LSP server 1.1.0-SNAPSHOT
VS Code 1.38.1
Language Support for Apache Camel by Red Hat - latest 0.0.18

Tested code:

<camelContext id="uitest-context" xmlns="http://camel.apache.org/schema/spring">
    <route id="uitest-route">
        <from id="_fromID" uri="timer:timerName?delay=1000r"/>
    </route>
</camelContext>

Result:
no detected errors in Problems view

Include UI tests in jenkins tests

currently UI tests re included in Travis build but not the Jenkins one.

when adding, check if the test report is provided (which is something that doesn't exist for Travis)

Improve test to get rid of the await sleep

camel-lsp-client-vscode/src/test/helper.ts

Line 21 in ea24ea1

await sleep(2000); // Wait for server activation

Provide test checking completion on Java file is available

Provide regression fix in changelog for default value completion and empty uri completion

see camel-tooling/camel-language-server#150

publish the vsix file to github

Improve contributing.md to explain how to start development

/!\ special npm install --ignore-script step (or find a way to get rid of it), maybe simply points to travis.yml file
maybe mention how to launch/debug in VS Code

Exclude dependabots branch from Travis build (except PR of course)

Upgrade dependencies to fix moderate security issues with lodash and js-yaml

npm audit
                                                                              
                       === npm audit security report ===                                                                                                       
# Run  npm install --save-dev [email protected]  to resolve 2 vulnerabilities                                                                                
  Moderate        Prototype Pollution                                                                                                                           
  Package         lodash                                                                                                                                  
  Dependency of   vsce [dev]                                                                                                                                    
  Path            vsce > cheerio > lodash                                                                                                                      
  More info       https://nodesecurity.io/advisories/782                                                                                                       


                                                                                
  Moderate        Prototype Pollution                                                                                                                         
  Package         lodash                                                                                                                                        
  Dependency of   vsce [dev]                                                                                                                                   
  Path            vsce > lodash                                                                                                                               
  More info       https://nodesecurity.io/advisories/782 

# Run  npm update js-yaml --depth 2  to resolve 1 vulnerability                                                                                
  Moderate        Denial of Service                                                                                                                            
  Package         js-yaml                                                                                                                                       
  Dependency of   tslint [dev]                                                                                                                                
  Path            tslint > js-yaml                                                                                                                              
  More info       https://nodesecurity.io/advisories/788

Support Java DSL for camel-k .java files in VSCode

when editing a .java file in camel-k style (no maven/eclipse project structure) the Camel Language Server does not recognize Java DSL (code completion)...

Find reference seems no more working

I used files from the tests content:

https://github.com/camel-tooling/camel-language-server/blob/cad0e3b7b2adf659bc0ec571115d021ce434f386/src/test/java/com/github/cameltooling/lsp/internal/references/MultiDocumentReferencesProcessorTest.java#L36-L66

create a travis job

Provide GitHub templates for new issues and PRs

Provide test checking navigation with Document symbol is working for XML

Ctrl+Shift+O

Fix incompatibility with Java Extension pack: same command name registered

there is the error mentioned here microsoft/vscode-java-pack#42

Upgrade tar dependency

to avoid reported vulnerability (it si affecting only dev so no risk but it will avoid to have a warning in github) and allows to detect more easily potential new vulnerabilities)

Generated vsix artefact doesn't contain the server jar

only the 0.0.1 tag from the 19 March is correct:

Provide test checking Camel completion is available

Provide test for high-level use case: Create Camel project/modify Java file/start locally

should we create the test inside this repository or another one as it goes beyond just Camel LSP but general Camel development?

create camel project:
-- which possibility to test first? maybe use git clone on https://github.com/jboss-fuse/fuse-rest-http-booster
modify Camel route Java file
-- check classic java completion available
-- check Camel completion available
use springboot dashboard related command to start the project

Modify project following move and split of repository

remove matrix from travis
update readme

Extention crashes on Windows (BUG)

Issue information

I am repeatedly gets this exception and it crashes

Exception in thread "main" java.lang.reflect.InvocationTargetException
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.base/java.lang.reflect.Method.invoke(Method.java:566)
	at org.springframework.boot.loader.MainMethodRunner.run(MainMethodRunner.java:49)
	at org.springframework.boot.loader.Launcher.launch(Launcher.java:107)
	at org.springframework.boot.loader.Launcher.launch(Launcher.java:58)
	at org.springframework.boot.loader.JarLauncher.main(JarLauncher.java:88)
Caused by: java.lang.NullPointerException
	at java.base/java.io.Reader.<init>(Reader.java:167)
	at java.base/java.io.InputStreamReader.<init>(InputStreamReader.java:72)
	at org.apache.camel.kafkaconnector.catalog.CamelKafkaConnectorCatalog.initCatalog(CamelKafkaConnectorCatalog.java:65)
	at org.apache.camel.kafkaconnector.catalog.CamelKafkaConnectorCatalog.<init>(CamelKafkaConnectorCatalog.java:52)
	at com.github.cameltooling.lsp.internal.catalog.util.CamelKafkaConnectorCatalogManager.<init>(CamelKafkaConnectorCatalogManager.java:23)
	at com.github.cameltooling.lsp.internal.CamelTextDocumentService.<init>(CamelTextDocumentService.java:94)
	at com.github.cameltooling.lsp.internal.CamelLanguageServer.<init>(CamelLanguageServer.java:53)
	at com.github.cameltooling.lsp.internal.Runner.main(Runner.java:65)
	... 8 more
[Info  - 11:24:59 am] Connection to server got closed. Server will restart.
Exception in thread "main" java.lang.reflect.InvocationTargetException
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.base/java.lang.reflect.Method.invoke(Method.java:566)
	at org.springframework.boot.loader.MainMethodRunner.run(MainMethodRunner.java:49)
	at org.springframework.boot.loader.Launcher.launch(Launcher.java:107)
	at org.springframework.boot.loader.Launcher.launch(Launcher.java:58)
	at org.springframework.boot.loader.JarLauncher.main(JarLauncher.java:88)
Caused by: java.lang.NullPointerException
	at java.base/java.io.Reader.<init>(Reader.java:167)
	at java.base/java.io.InputStreamReader.<init>(InputStreamReader.java:72)
	at org.apache.camel.kafkaconnector.catalog.CamelKafkaConnectorCatalog.initCatalog(CamelKafkaConnectorCatalog.java:65)
	at org.apache.camel.kafkaconnector.catalog.CamelKafkaConnectorCatalog.<init>(CamelKafkaConnectorCatalog.java:52)
	at com.github.cameltooling.lsp.internal.catalog.util.CamelKafkaConnectorCatalogManager.<init>(CamelKafkaConnectorCatalogManager.java:23)
	at com.github.cameltooling.lsp.internal.CamelTextDocumentService.<init>(CamelTextDocumentService.java:94)
	at com.github.cameltooling.lsp.internal.CamelLanguageServer.<init>(CamelLanguageServer.java:53)
	at com.github.cameltooling.lsp.internal.Runner.main(Runner.java:65)
	... 8 more
[Error - 11:25:01 am] Connection to server got closed. Server will not be restarted.

Define issue title short and most specific to the problem.

Tag each new issue with relevant LABELS (Bug, Improvement, etc.).

BUG report

Environment

Language Support for Apache Camel version: e.g. "v0.0.13" ?
v0.0.28
OS:
- Linux (RHEL, Fedora, Ubuntu, ...)
- [ X] Windows
- macOS

Description of wrong behavior

Exact steps to reproduce issue

Opening camel project with maven
...
...

TASK definition

Description

These are dependencies in pom.xml

<dependencies>
        <dependency>
            <groupId>org.apache.camel.springboot</groupId>
            <artifactId>camel-spring-boot-starter</artifactId>
        </dependency>
        <dependency>
            <groupId>org.springframework.boot</groupId>
            <artifactId>spring-boot-configuration-processor</artifactId>
        </dependency>        
        <dependency>
            <groupId>org.apache.camel.springboot</groupId>
            <artifactId>camel-kafka-starter</artifactId>
        </dependency>
    </dependencies>

Camel version is 3.4.4

Expected behaviour

There should be no error

Screenshot (optional)

Configure build to provide test coverage in Sonar

our first test is coming, now it will be nice to be able to see a part of the coverage #33

offer extension at vscode plugin repo

Upgrade tslint to 3.5.1+

                       === npm audit security report ===                        
                                                                                
# Run  npm update underscore.string --depth 2  to resolve 1 vulnerability
                                                                                
  Moderate        Regular Expression Denial of Service                          
                                                                                
  Package         underscore.string                                             
                                                                                
  Dependency of   tslint [dev]                                                  
                                                                                
  Path            tslint > underscore.string                                    
                                                                                
  More info       https://nodesecurity.io/advisories/745

[ENH] Improving activating whitelist support for Java DSL

According to yesterday's article, there is currently a set of pre-requisites for the functionality to be enabled:

The filename needs to end with .java.
The file needs to contain camel written somewhere.
The Camel URI String needs to be used directly as a parameter of the RouteBuilder.from or RouteBuilder.to methods (which means no space, no variable).

This is understood but it would be useful exposing the user the logic to activate the functionality.

I assume the .java suffix is an hard constraint, despite I think it should be useful to allow a way to enable the plugin also on disposable temporary new files, that don't have any file name yet.

The most limiting constraint is the camel keyword requirement. I was about to suggest to switch to route, but at that point, I've realised that probably the real feature would be to allow the user to specify the regexp/GLOB/keywords they like.

Activate Sonar analysis

Provide a Camel Extension Pack

which will gather several useful plugins for Camel development, for instance:

Java Extension pack
Spring Boot Extension pack
XML support by Red Hat (?)
fabric8-launcher?
yeoman integration?

Support loading Language Server from java.home specified in VS Code settings (avoid to fail to load when `java` isn't in `$PATH`)

Issue informations

BUG report

Environment

Apache Camel Language Server release version: 0.0.22
OS:
- Linux (RHEL, Fedora, Ubuntu, ...)
- Windows
- Mac OS
Apache Camel Client for:
- Eclipse
- VS Code
- Eclipse Che
- OpenShift.io

Description of wrong behavior

The language server fails to start if the java binary is not found in $PATH. That is despite $JAVA_HOME being defined in the environment and java.home being defined in VScode settings.

Exact steps to reproduce issue

Install VScode OSS from FlatHub (This means it will not ave access to the system Java)
Install Java via e.g. sdkman into a location in $HOME.
Set the java.home setting in VScode to point to where JAva is installed (This is enough to enable the Java language server to load in VScode)
Install the Camel language extension

TASK definition

Description

Respect the $JAVA_HOME environment variable and the java.home setting when starting up the language server

Expected behaviour

When starting up the language server, search for the java binary in $JAVA_HOME and java.home.

remove publish from Travis config
change icon
change publisher in package.json
provide jenkins pipeline config (example here https://github.com/redhat-developer/vscode-project-initializer/blob/master/Jenkinsfile)

camel-tooling / camel-lsp-client-vscode Goto Github PK

camel-lsp-client-vscode's People

Contributors

Stargazers

Watchers

Forkers

camel-lsp-client-vscode's Issues

Issue information

BUG report

Environment

Description of wrong behavior

Exact steps to reproduce issue

TASK definition

Description

Expected behaviour

Screenshot (optional)

Issue informations

BUG report

Environment

Description of wrong behavior

Exact steps to reproduce issue

TASK definition

Description

Expected behaviour

Recommend Projects

Recommend Topics

Recommend Org