-
Notifications
You must be signed in to change notification settings - Fork 72
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
[Feature request] Helm chart syntax highlighting support #329
Comments
That can be investigated. Do you have an example of Helm Chart to share? Are those Yaml files? what's their usual name patterns? Is there a schema for those somewhere? |
Basically, helm charts consist of template files (.tpl) , which are still the kubernetes yaml files with the placeholders in double curly braces. The values for the placeholders should be stored in the |
I think this would need to be supported in the https://github.com/redhat-developer/yaml-language-server used by Wild Web Developer. I've opened redhat-developer/yaml-language-server#220 to request that. |
@mickaelistria the initial issue is about syntax highlight for helm. I think WWD should embed https://github.com/Azure/vscode-kubernetes-tools/blob/master/syntaxes/helm.tmLanguage.json And if you see https://github.com/Azure/vscode-kubernetes-tools/blob/127ec070c8dabd56901ce13ff81bd6f561e4f087/src/yaml-support/yaml-schema.ts#L36 it uses the To do that we need #318 and it's a work that I have started in https://github.com/angelozerr/wildwebdeveloper/tree/yaml-custom-schema In otherwise it seems |
You can use my plugin https://github.com/sebthom/extra-syntax-highlighting-eclipse-plugin to get jinja and helm chart syntax highlighting. |
Hi there.
I'm using WWD almost a year because of excellent Kubernetes scheme support.
It would be great to have the Helm charts syntax highlighting support too, because Helm de facto is the most common package manager for Kubernetes.
Are there any plans around this in your roadmap?
Thanks
The text was updated successfully, but these errors were encountered: