-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Comments
It turns out that conda's 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. |
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. |
https://conda.io/docs/user-guide/tasks/build-packages/define-metadata.html
The text was updated successfully, but these errors were encountered: