Open ekingery opened 4 years ago
The code changes for linting should be fairly straightforward, but I'm concerned about the scope of the repercussions to the rest of the features (fmt, tree, generate). This is not yet an informed opinion, but my gut says that it might be faster and easier to essentially rewrite these tools using json-schema (or maybe joi) as suggested in #152. For your consideration, @ErikSchierboom.
The code changes for linting should be fairly straightforward, but I'm concerned about the scope of the repercussions to the rest of the features (fmt, tree, generate). This is not yet an informed opinion, but my gut says that it might be faster and easier to essentially rewrite these tools using json-schema (or maybe joi) as suggested in #152. For your consideration, @ErikSchierboom.
I like the idea of using JSON schema to validate the track config.
@ErikSchierboom I wanted to get this PR going early so that you could validate the V3 changes to the
fixtures/lint/valid-track/config.json
before I spend too much time writing code against them.