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

Provide a schema for the new config? #42

Open
danielcompton opened this issue Aug 15, 2018 · 3 comments
Open

Provide a schema for the new config? #42

danielcompton opened this issue Aug 15, 2018 · 3 comments
Labels
enhancement New feature or request planned Something we plan to do in the foreseeable future

Comments

@danielcompton
Copy link
Contributor

danielcompton commented Aug 15, 2018

I use the schemas defined in SchemaStore to help validate the CircleCI config that I write, via the RedHat VSCode YAML extension. It would be useful if this new config version was schemafied and added to the schemastore. I imagine this might only make sense once the config format is finalised though. SchemaStore/schemastore#515

Update: It looks like there is a schema already:

Configuration for the build is validated to ensure it parses as YAML and adheres to the CircleCI configuration schema (TODO: publish and link to the schema). - config-lifecycle

@johnswanson
Copy link
Contributor

We'll definitely be doing this once we're positive that the schema for 2.1 is finalized--thanks for the heads up about schemastore!

@ndintenfass ndintenfass added enhancement New feature or request planned Something we plan to do in the foreseeable future labels Aug 24, 2018
@JCMais
Copy link

JCMais commented Apr 19, 2019

any updates here @johnswanson ?

@kevinswarner
Copy link

I am getting VS Code YAML errors relating to 2.1 command parameters. Getting 'Incorrect type. Expected "string".' error in the config for calling a command with a parameter value. I believe it is that the schema is not updated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request planned Something we plan to do in the foreseeable future
Projects
None yet
Development

No branches or pull requests

5 participants