add mojito configuration schemas #1054

wants to merge 2 commits into

4 participants


This pull request adds mojito configuration schemas. These schemas are in compliance with IETF json schema draft, and are defined according to The related code change has been sent to mojito-cli repository.


I will argue that the schemas should not be part of mojito source, but part of mojito-cli-validate or something similar but not core. We can also explore a similar approach to the one we have lineup for the initial archetypes that can bring some default npm devDependencies that can be used by cli to resolve few other things.


The configuration of mojito keeps evolving, accordingly these schemas will change with each version of mojito. I think it makes sense for the shemas to be part of mojito, and the validate command to be part of mojito-cli, so that the user can use a single "mojito validate" command to validate all his mojito applications.


We asked @Yujun-Qian to have the schemas included with core mojito source, which makes the most sense at this point-- especially if we think it will be changed.

I also think we must validate our test apps against the mojito schemas in CI. +1

@Yujun-Qian Yujun-Qian referenced this pull request in yahoo/mojito-cli Apr 12, 2013

add "validate" subcommand #9

@imalberto imalberto closed this Feb 25, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment