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

Newer/older Kubernetes schemas break autocompletion/diagnostics #778

Open
someone-stole-my-name opened this issue Sep 17, 2022 · 3 comments · May be fixed by #841
Open

Newer/older Kubernetes schemas break autocompletion/diagnostics #778

someone-stole-my-name opened this issue Sep 17, 2022 · 3 comments · May be fixed by #841

Comments

@someone-stole-my-name
Copy link

Summary

While debugging someone-stole-my-name/yaml-companion.nvim#12 we've seen some bizarre behavior. One would expect yaml-language-server to work with Kubernetes schemas higher or lower than the one hardcoded if the user explicitly adds them, but that's not currently the case. Bumping even the patch version seems to break diagnostics and autocompletion behaves differently despite 1.22.4 and 1.22.5 being the same, e.g.

{
    "yaml.schemas": {
        "https://raw.githubusercontent.com/yannh/kubernetes-json-schema/master/v1.22.5-standalone-strict/all.json": "/*.yaml"
    }
}

With 1.22.5 the following document doesn't display the expected Property foo is not allowed.

apiVersion: networking.k8s.io/v1
kind: Ingress
foo: bar

And autocompletion is not working correctly either. Anything under spec: is not autocompleted as it does in 1.22.4:

apiVersion: networking.k8s.io/v1
kind: Ingress
spec:

Related:

@devodev
Copy link

devodev commented Jan 21, 2024

Bump ?

@smthbrothrjdev
Copy link

I am having the same issue. Has anyone found a more permanent work-around besides the one listed here ?

@mosheavni
Copy link

same issue here. can it be fixed?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants