-
Notifications
You must be signed in to change notification settings - Fork 9
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
Completion in k8s files #7
Comments
I think you don't need to find and add some more. Just see what you need and just make it become a yasnippet template.
Helm template is jinja file, so if you want to support helm, you should write a new helm-k8s-mode (because helm-mode name had taken) instead of using this mode |
Although I do agree that creating a yassnippet is convenient, I am still early in my journey and what I need is still kinda hard to determine. I was thinking of writing a completion backend with docs so that people like me can see the purpose of what they are using. Completion in kubernetes for the key values would be really helpful but it's a little difficult considering the contextual dependency of nested keys. Like spec can be a key under templates & service at two different levels. |
If I understand correctly, seems you should learn about company-mode for the completion feature. You will have to write a new company-backend function |
Do you know of a way to get completion added? I would be willing to add some for this mode, but I do not know where I would find the keywords for kubernetes files. Also do you plan to do anything with Helm in the future?
The text was updated successfully, but these errors were encountered: