Not sure if this fits with the goals of the project but I think it would be nice to have an interactive mode based on a project's default .json file. Lots of project setup tools have a way to just specify an output dir, some template and then it will prompt you for all info it needs. To me this is a much more natural approach than creating a json file, comparing it against the default one, writing it up and then generating your file.
I'd imagine if the project had a sample.json like
{
"description": "Template for a project",
"context": {
"project": "example",
"author": "Mustachioed Maven"
}
}
Then with an -i flag or something, molt could take that file and produce the following output:
description: my cool project
Context
project: coolproj
author: me!
It could even use existing non-null values in the json file as defaults or examples. What do you think?
Not sure if this fits with the goals of the project but I think it would be nice to have an interactive mode based on a project's default .json file. Lots of project setup tools have a way to just specify an output dir, some template and then it will prompt you for all info it needs. To me this is a much more natural approach than creating a json file, comparing it against the default one, writing it up and then generating your file.
I'd imagine if the project had a sample.json like
{ "description": "Template for a project", "context": { "project": "example", "author": "Mustachioed Maven" } }Then with an -i flag or something, molt could take that file and produce the following output:
It could even use existing non-null values in the json file as defaults or examples. What do you think?