-
Notifications
You must be signed in to change notification settings - Fork 667
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
Choosing bootstrap generates vendor.scss in app, but using angular-material doesn't. #439
Comments
Same problem here. |
The error are in WireDep Fixed by doing this. |
No, not quite. I updated my issue |
In my case I needed to add
|
@robertbaker |
I have it in another issue I created. Through bower, in my bower json. The solution is to reference scss in vendor.scss so this bug is really the generator not making a vendor.css if angular-material is chosen, even though SASS is. |
ok. Thanks |
angular-material doesn't provides SCSS. |
The issue is the generator does not create the vendor.scss file (and related gulp config) if angular-material is chosen, but SASS is. Vendor scss and config should be generated if SASS is selected. Right now it's dependent on bootstrap sass being selected. IMO vendor.scss should be generated if the SASS option is selected. Right now it's only being generated if sass AND bootstrap-sass are selected. |
Why you want a |
That's the only way to import any SASS from bower_components. Just because I'm not using bootstrap, doesn't mean I'm not going to use any other bower packages that do use SASS. Currently SASS files are ignored during injection, even if they are specified in the bower.json. The only way I found to use SASS from bower_components is to import the file in vendor.scss. Which does not exist (and the gulp config that goes with it) unless you specify bootstrap-sass. You should get the capability to use the vendor.scss file if you choose a SASS option. If you don't need to import any sass from bower_components, the file just goes unused Why wouldn't you want vendor.scss, bootstrap isn't the only bower package that uses SASS. It seems counter intuitive to only include vendor.scss if you choose bootstrap, when it doesn't need bootstrap at all. It's a feature tied to SASS and thus should be given if you choose a SASS option, not just the bootstrap SASS option. |
Ok I got it. As angular-material doesn't link the sass version in its bower.json, we consider that there is no need of using a vendor.scss. It's the case at the moment of the initialization but I agree that you could have use for it anyway later. In fact, we shouldn't assume anything and create all the files even when the main framework chosen can't use all the features. About the lib "material-design-iconic-font" in particular, you'll still have to make your awn adjustments as there is several material icons lib and I'm not sure we want to include this one by default. |
@Swiip I'll try to find some time to give a repro case.
What is the use case for vendor.scss file, if wiredep can inject scss? |
The new mechanism is that wiredep inject scss deps in vendor.scss... |
I'm using material-design-iconic-font
Chose all angular options, for framework choose Angular-Material.
choosing bootstrap generates vendor.scss in app, but using angular-material doesn't.
Using .010
suggested fix:
---
The text was updated successfully, but these errors were encountered: