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

FUSETOOLS2-2508 - Do not register the Camel Language Server for package.json file #2030

Conversation

apupier
Copy link
Member

@apupier apupier commented Dec 4, 2024

every two minutes, there are events didOpen and didClose for package.json files (not found the reason).
It is polluting Camel logs. Potentially leading to killing the server. Given that the Camel Language server does not provide anything for package.json files, the workaround consists in providing a more strict document selector to discard package.json. As json file, we provide completion only in VS Code launch.json and tasks.json files.

package.json

every two minutes, there are events didOpen and didClose for
package.json files (not found the reason).
It is polluting Camel logs. Potentially leading to killing the server.
Given that the Camel Language server does not provide anything for
package.json files, the workaround consists in providing a more strict
document selector to discard package.json. As json file, we provide
completion only in VS Code launch.json and tasks.json files.

Signed-off-by: Aurélien Pupier <[email protected]>
@apupier apupier force-pushed the 2508-avoidBeingPollutedByPackage.JsonDidCloseDidOpenEvents branch from 8c3bb13 to e41ea93 Compare December 4, 2024 09:51
Copy link

sonarcloud bot commented Dec 4, 2024

@apupier apupier changed the title FUSETOOLS2-2508 - Do not register the Camel Language Server for package.json FUSETOOLS2-2508 - Do not register the Camel Language Server for package.json file Dec 4, 2024
@apupier apupier merged commit 8e0f203 into camel-tooling:main Dec 4, 2024
20 checks passed
@apupier apupier deleted the 2508-avoidBeingPollutedByPackage.JsonDidCloseDidOpenEvents branch December 4, 2024 12:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants