Setup TravisCI and lint at least datasets.yml
Closed this issue · 5 comments
@edsu do you have a preferred yaml linter? I'm looking at these two:
...I'm leaning towards the first one.
I guess I was thinking it would be useful to read the YAML file and make sure each dataset seems complete: has a title, url, etc. I think that would cover invalid YAML since it wouldn't parse right?
But maybe this is more than you imagined doing? Happy to start with basic "it will parse".
We could do multiple "tests". First would be whether or not it lints, the second would be does it have required fields.
Doing the second requires parsing the yaml, which is basically linting it..or at least what I'm imagining linting would do as you describe it. Or would linting do something else?
Oh, linting for me just means is valid/well formed according to the specification. The second step would be ...schema validation?