Gorkem Ercan

@jpinkney-aws > @gorkem Do you know who owns this after you've left red hat? 🤷 probably under staffed

Looks like this is missing the documentation. If I recall correctly, it is a custom document [like this example](https://github.com/redhat-developer/yaml-language-server/blob/762209ccdfca713d203ead757698a47ad3cabf50/test/fixtures/customMultipleSchemaSequences.json) which is referenced like a regular schema from options.

I can not replicate this issue. Can you provide a more complete example?

Are you shipping `yaml-language-server` as part of your solution?

what is the language identifier for pulumi.yaml? If it is YAML, at least vscode will activate it. we do list * .yaml files but I suspect even without us listing...

What kind of conflicts do you get? Is there a schema associated somehow with pulumi files. If that is the case, you can try to set it to a dummy...

How would the LS coordinate this with the editor features? VSCode, for instance, has settings to enable and configure tab-to-space conversion.

Does the jsonSchema specification have patterns as arrays with the additional fields that you have added here? I can not seem to find a reference to it.

Correct, item uniqueness is determined by the [schema](https://json-schema.org/understanding-json-schema/reference/array#uniqueItems). The current implementation does not take into account the `uniqueItems` flag. An improvement to the current implementation would be checking this flag...

I do not think the current behaviour is incorrect in this case. In YAML, empty values [are recognized as null ](https://yaml.org/spec/1.2.2/#1032-tag-resolution). So the parser basically reports the value as null,...