-
Notifications
You must be signed in to change notification settings - Fork 334
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
yaml validator for presentations.yaml #142
Comments
As part of this make the |
What do we do in cases where there's no slides, video only? Do we just make having slides a prerequisite? |
We had previously discussed making the slides field required. I am now keying off that field during the import process. If we don't make it required, then I'll need to key off some other field that is always required and guaranteed to be unique for each presentation. Alternatively, I could come up with some kind of composite field, made up of video + slides fields, to use as a unique key. Any thoughts? |
@cjyabraham I'd do slides+date as a composite field. We don't currently require videos (but if we could I can add that too and we can add that to said composite field) |
Also you may want to limit the possible |
We need a validator for
presentations.yaml
before we open it up to submissions.The text was updated successfully, but these errors were encountered: