Hi

Maybe I've missed it, but for now it seems to be impossible to namespace variable.

It would be great to use options.name or additional options value for that purpose, so in result we could get instead of

$car-blue: blue;
$car-red: red;

namespaced variables, like:

$myJSON-car-blue: blue;
$myJSON-car-red: red;

Hi

First of all, thanks for great product!

It seems that Sass maps generation has some issues due to lack of quotes.

For example, following generated Sass map will through an error:

$grunt-data: (
    site: (
        lang: en,
        name: Kotsu,
        title: Clean, opinionated foundation for new projects — to boldly go where no man has gone before,
        version: 0.5.3
    )
);

Error: Invalid CSS after "...has gone before": expected ":", was ","
        on line 5 of C:\Working\Kotsu\temp\styles\config.scss
        from line 34 of source/styles/style.scss

getStyleSafeValue doesn't produce the expected output for arrays when output to the value of a key in a Sass map

Consider this source data:

// with options.name = 'grids' & options.useSassMaps = true
{
    "base": {
        "gutter": 15,
        "columns": 12,
        "output": [ 2, 10, 12 ]
    }
};

This currently results in the Sass output:

$grids: (
    base: (
        gutter: 15,
        columns: 12,
        output: 2,10,12
    )
);

This will cause a parse error in Sass, as , is used both as a list separator, and to denote the end of a map key's value.

The expected output would wrap list/array output in parens to avoid this ambiguity:

$grids: (
    base: (
        gutter: 15,
        columns: 12,
        output: (2,10,12)
    )
);

Happy to take a crack at this one if a PR would be considered, but #25 suggests you're looking refactoring getStyleSafeValue anyway, so thought I'd open an issue first.

Sass Maps are currently produced in an almost minified manner. Since the JS formats are printed in formatted style, so should the sass maps.

When using a string as a value in the src JSON file,

{ "key": "value" }

the string "value" will be output as null in the generated javascript file.

define( function() { return { "key": null } });

Can the script be updated to correctly translate strings to the javascript output?

I think it would be great to be able to specify wildcards in source/destination:

src: "config/*.yml",
   dest: [
      "styles/config/*.sass",
      "scripts/config/*.json"
   ]

The expected behaviour would be that for each yml file, a sass and json file (with the same name) would be created as well.

What do you think?

You can remove a dep, mout, if you wanted as your usage is covered by grunt.util._ and grunt.util._.str. If you're interested I can do a PR.

theo is very similar to shared config. But they use templates for the different outputs. This could be great feature for shared config as well. And would be easy to do with HBS files:

https://github.com/salesforce-ux/theo/tree/master/templates

I could use output to angular constant. I was using grunt-ng-constant against the same json files, but I also need your unit stripping.

I'll submit a pull request, at least until GH-18 is resolved.

Great module btw :)