'preprocessCss' not respecting EmberApp's name same as 'preprocessJs'

[bockscar]

New to ember-cli and not yet acquainted with codebase. Pull request would've been nice, but I couldn't figure out how to get to info I needed.

With an app set up something like this:

var app = new EmberApp({ name: 'ArbitraryNameFred' });

I would expect built assets named ArbitraryNameFred.js and ArbitraryNameFred.css.

The former file is named in abidance of the name key per app instantiation. However the latter defers to the package.json name and not the app's instantiated name.

This happens in preprocessCss which builds the path via 'assets/' + pkg.name + '.css' wherein pkg is package.json. The complication arises when multiple calls to preprocessCss are made but the output filename is different than the Javascript filename output.

This seems like it should be an easy fix, but I am not seeing where the EmberApp object is accessible from preprocessCss...so maybe it is not so easy.

Or perhaps this is the desired behavior, i.e., wired into package.json. Hopefully that is not the case as it greatly reduces flexibility. But if so, it'd probably reduce confusion if Javascript output abided by same convention.

Look forward to getting in more pull requests as I gain familiarity with this setup....

[stefanpenner]

this may be fixed on master

[bockscar]

Nah, master still references "pkg.name" as described above. Situation unchanged.