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

JSON schema for conda's meta.yaml #281

Closed
brettcannon opened this issue Nov 23, 2017 · 2 comments · Fixed by #291
Closed

JSON schema for conda's meta.yaml #281

brettcannon opened this issue Nov 23, 2017 · 2 comments · Fixed by #291
Assignees
Labels
feature-request Request for new features or functionality
Milestone

Comments

@brettcannon
Copy link
Member

https://conda.io/docs/user-guide/tasks/build-packages/define-metadata.html

@brettcannon brettcannon added awaiting 2-PR feature-request Request for new features or functionality labels Nov 23, 2017
@brettcannon brettcannon added this to the December 2017 milestone Nov 23, 2017
@brettcannon brettcannon self-assigned this Nov 23, 2017
@brettcannon
Copy link
Member Author

It turns out that conda's meta.yaml files can contain Jinja templating, which makes them (potentially) invalid YAML. It also makes all keys basically just strings.

That means either Jinja templating is viewed as an error, global Jinja is an error but per-item is set up to support at least strings everywhere, or we just don't worry about schema support.

Attached is a schema with strong typing when I realized that maybe it was the wrong approach.

conda-meta.zip

@brettcannon
Copy link
Member Author

In the end I decided to make all fields an explicit type + "string" so that it was at least somewhat useful. Plus all the property names are there to help with intellisense.

@lock lock bot locked as resolved and limited conversation to collaborators Jul 12, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
feature-request Request for new features or functionality
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants