Implement link checker and other server side validation on Travis

iilab / contentascode

Content as Code

http://iilab.github.io/contentascode

GNU General Public License v3.0

34 stars 7 forks source link

Implement link checker and other server side validation on Travis #11

Open jmatsushita opened 8 years ago

jmatsushita commented 8 years ago

Feeding into #7 implementing a server side link checker would be a good PoC. What would be even better is an isomorphic link checker.

jmatsushita commented 8 years ago

Validating keys for SPAR standard compliance would be another client side/server side validator need. #12

jmatsushita commented 8 years ago

Another possible CI test that would be useful if the management of tags is open, it provide feedback on sparseness of tags to help improve the usability and relevance of more fluidly defined and evolving taxonomies.

jmatsushita commented 8 years ago

@gembarrett Would love to hear your thoughts on how to include style guide as a validator!

jmatsushita commented 8 years ago

Given how Travis actually only shows a canned The Travis CI build failed message on pull requests via the Commit Status API, it might be better (and more in line with the overall micro-service approach) to develop (or wrap or automate) our own CI service this would help in being able to do browser based tests (although might still need some isomorphic smarts or local deployment to deal with offline use).

jmatsushita commented 8 years ago

It's working on the init project!

jmatsushita commented 8 years ago

The ProseMirror linting demo is awesome and MarkdownLint is interesting.