Josh Pinkney

cc @eclipse-theia/plugin-system

@akosyakov You can take a look again!

Yes I believe so. But TBH I question if we should even have the kubernetes schema embedded in this extension anymore and should just tell people to add it if...

@joshrosso Yeah, this language server originally started (3~ years ago) as a kubernetes language server and once we found out that the support for kubernetes worked well we expanded it...

Are you able to access https://raw.githubusercontent.com/instrumenta/kubernetes-json-schema/master/v1.17.0-standalone-strict/all.json directly? Are you behind some proxy?

It depends. In some cases that error occurs when a schema is written in a way that allows multiple subschemas to match one piece of content. For example, in kubernetes:...

I think its an issue with the schema. The problem is there are so many subschemas inside of the kubernetes schema that it makes issues with the schema almost impossible...

We don't currently have a cli but if someone wanted to build one it would be pretty easy. You could create a new language service like what's done here: https://github.com/redhat-developer/yaml-language-server/blob/04bfdccaada7724469c76e3319a26d0a4b096de6/src/yamlServerInit.ts#L61...

In order to test the issue you can set the trigger character to " " and then you can set the schema to be kubernetes then have ``` apiVersion: v1...

I think at this point the problem is that when performing auto completion it will sometimes show bogus results that when you auto complete them it will result in errors....