-
Notifications
You must be signed in to change notification settings - Fork 41
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
New builtin schema type: CITATION.cff? #502
Comments
I'm generally pretty open to adding new schemas, so sure! (I'd like to get all of schemastore included at some point, but there are a few problems associated with that.) If you want to open a PR, I think I have the process documented in the contrib doc. Or I can look at this when I'm back next week. The only thing which might need special handling is the
It is using the name, yeah. 😢 I would still like to have a cache which can be navigated without a special tool, so I will probably do something like...
Or maybe a small SQLite DB. |
I've got a mostly automatic mirror of the pyproject.toml part of SchemaStore at https://github.com/henryiii/validate-pyproject-schema-store, it might look something like that. The .cff file is JSON. It's not recognized as JSON automatically since it's an overloaded extension. This file, though, will always have the base name CITATION. I can do it eventually, but it might be a week or two. |
Would it make sense to add CITATION.cff to the built-in schemas? It would be nice to have a flag and a pre-commit check for it, currently it requires:
and
(This also doesn't work for pre-commit.ci, it can't pull this file, being built-in should fix that)
Ref for CITATION.cff: https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files and links from there. Most notably, https://github.com/citation-file-format/citation-file-format/blob/main/schema-guide.md#definitionsreferencedate-published. The link above is from SchemaStore.
PS: I'm not sure why
--no-cache
is required, it gets a completely incorrect file if not passed. Maybe it's caching on the nameschema.json
?The text was updated successfully, but these errors were encountered: