Gruntfile about generator-jam3 HOT 4 CLOSED

We should switch the gruntfile generation to be created by the gruntfile editor built into yeoman.

http://yeoman.io/authoring/gruntfile.html

Currently there's an issue because yeoman and grunt both use lodash/underscore templating. This leads to both using the same <%= %> for instance.

from generator-jam3.

I was starting this task using the yeoman gruntfile editor, but it is getting configurations as String, so it is quite complicate to create a big gruntfile...

There is not an issue about lodash/underscore templating. The template system make the difference:

<%= %> ---> when you are using template from outside...
<%%= %> ----> When you want to include internal configurations.

Anyways I agree with using yeoman gruntfile editor, we should just find a nice way to it be readable and easy to maintain.

from generator-jam3.

@miguelmoraleda i know i read that in the docs also. but in practice it wasn't working :( So I refactored it to work for the time being. Earlier today I was able to get a project up and running 100% where I could edit code and everything. Also it's implemented that you can update the model/index.js and call yo jam3:update to create new sections/templates.

from generator-jam3.

@mikkoh cool, anyways it was working for me...FYI: I couldn't use it with your template function... but using this.template works perfectly. The problem is that on your template function you are using templatePath instead of template

from generator-jam3.