Open igbopie opened 5 years ago
Could you provide a more detailed example. As that way we can see exactly what you are expecting (input/output).
As eyeglass allows for some additional conventions, it may not be possible to preserve the above semantics in all scenarios. By seeing yours we can provide a more accurate response/fix/idea/doc-fix
Sure, in the example provided
outputPaths: {
app: {
html: 'index.html',
css: {
'app': '/assets/css/application-name.css'
},
js: '/assets/js/application-name.js'
},
vendor: {
css: '/assets/css/vendor.css',
js: '/assets/js/vendor.js'
}
}
the file application-name.css
won't appear under assets/css
but assets
.
The problem is that here:
it is taking outputPath variable which is always assets
according to this code:
Instead, the fourth parameter should be used which includes the 'outputPaths' specified in the config.
@stefanpenner IMO, preprocessors shouldn't have to know the internals of ember-cli's configuration. IMO eyeglass should translate .scss to .css and then ember-cli should do these renames on the css files according to the config that it is in charge of implementing.
Package This issue is related to the following monorepo package(s):
Description Ember-cli-eyeglass does not respect outputPath configuration like the example in ember docs:
https://ember-cli.com/user-guide/#configuring-output-paths
To Reproduce Steps to reproduce the behavior:
Expected behavior Css file should show in the right location