No ability to do easy glob wildcards of files about grunt-template

[eskelter]

@mathiasbynens did he part :) We can easily do what you ask for ourselves:

install node-glob in your project (e.g. npm i glob --save-dev)

then in your gruntfile.js :

var glob = require('glob');

// ...

template: {
    
    some_target: {
        
        // options: { ... },
        
        get files () {
            
            var result = {};
            
            glob.sync('app/**/*.js.tpl').forEach(function (file) {
                
                this[file.replace(/\.tpl$/, '')] = file;
                
            }, result);
            
            return result;
            
        }
        
    }
    
}

[mhintzke]

Oh interesting I was not aware this was possible. Is there any documentation that says we are allowed to use a function in place of the 'files' object? Thanks for the help though.

[eskelter]

This is a getter, not a function per se.

It is implemented as a function, but exposed a regular property value. So as far as grunt is concerned, { get files () { return ['value']; } } is the same as { files: ['value'] }: It sees the file property as an Array in either case.

This getter/setter syntax was popular before Object.defineProperty became all the rage (and the standard :-). The latter does offer much more flexibility, but get/set still looks cleaner when your don't need any fancy feature. Let's not even talk about defineGetter :-P

[mhintzke]

Ah I see, I have used getters and setters in C# before but didn't realize they were actually a legacy construct of JS (rather I thought they were ES6+ features). Guess you learn something everyday :) Thanks