-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Glob paths when resolving CSS dependencies #21
Comments
I'll take a look. Globbing should work. |
Where are you seeing that |
I put a debug($path) statement before line: |
Ok. Which less filter are you using? |
LessCss. |
OK, I'll see if I can reproduce this problem on my side. |
I've just looked at the AssetScanner tests too and that's not where the problem lies. See this back trace and you'll see there's no AssetScanner involved. AssetScanner correctly expands the glob paths at initialization but the CssDependencyTrait code doesn't use that, it uses the raw paths instead.
For my case I've solved it using a directory path without stars, but since it's a deviation from the expected behavior I guess it should be fixed or at least warn about this caveat. |
Thanks for that tip. I'll take a look. |
Expand paths before creating asset targets. This ensures that paths have been expanded when filters get configured from the asset target. Refs #21
Pull request up now. Looks like this was caused by how asset targets were created. They were being created with un-expanded glob paths. |
I think glob paths don't work when resolving CSS dependencies. The function that searches the file uses file_exists directly on the path setting and the file name.
This will check for the file "WEBROOT/css/*/public/base.less".
The text was updated successfully, but these errors were encountered: