kind, name and steps are not recognized as yaml properties

When opening my Drone CI yaml file, errors are given about the keys kind, name and steps not being valid properties. The opened file is a valid drone yaml file, so I guess there is no support by this extension.

Would support for those keys be added in the future? In case the problem is another, any useful pointer would be greatly appreciated

[zerosym]

@HitLuca Upon closer inspection it might be an issue for here after all. The schema file in schemastore repo seems up to date (was last pushed only a couple weeks ago) and I’ve had luck with validating my own drone.yml file by modifying the schema slightly. Specifically, the lack of a top level “properties” key seems to be causing the validator issues, even though an array of them is defined under “oneOf”.

It could be because the drone schema implements the latest version of JSON spec which may not be fully implemented yet in vscode-yaml (https://github.com/redhat-developer/vscode-yaml/issues/222).

It’s either that or the schemastore spec for drone is incorrectly written – I don’t have the knowledge to tell either way.

[JPinkney]

AH! I finally figured it out. It ended up being a schema issue but this was one of the oddest bugs I’ve had to track down.

So it turns out that the drone schema sets additionalProperties to false for the root object: https://github.com/SchemaStore/schemastore/blob/master/src/schemas/json/drone.json#L4

According to the json schema spec:

The additionalProperties keyword is used to control the handling of extra stuff, that is, properties whose names are not listed in the properties keyword.

In the schema there is no root properties keyword, meaning that everything is considered an additional property and that’s why the errors appear.

I’m going to send a PR to the json schema store and close this issue.