-
Notifications
You must be signed in to change notification settings - Fork 6.8k
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
Material schematics doesn't work with configured angular schematics (scss, spec, etc...) #11874
Comments
pre-built themes are fully baked themes i.e.e they will be css not scss. PS: I take it back. I think you are talking about the generated dashboard styles which are css not scss which is the issue. |
I don't mind that pre-built themes are .css. It's normal. If I want use custom theme I can do it. |
Seems that for now you must specify The schema.json for this setting just accepts any file extension it seems. |
It should be reading from your cli configuration. Can you verify that? |
Sounds like this is a similar issue as #12881 ? |
Since 5144aa7, we already respect the |
… spec option value If developers create a new Angular CLI project, options like `--skipTests`, `--inlineTemplate` or `--inlineStyle` can be specified. These options will be stored in the workspace config file and will be respected if someone generates another component on the existing project. Since we technically also generate components, we should respect the default option value for those options if _not_ explicitly specified. Closes angular#11874.
… spec option value If developers create a new Angular CLI project, options like `--skipTests`, `--inlineTemplate` or `--inlineStyle` can be specified. These options will be stored in the workspace config file and will be respected if someone generates another component on the existing project. Since we technically also generate components, we should respect the default option value for those options if _not_ explicitly specified. Closes angular#11874.
… spec option value (#12888) If developers create a new Angular CLI project, options like `--skipTests`, `--inlineTemplate` or `--inlineStyle` can be specified. These options will be stored in the workspace config file and will be respected if someone generates another component on the existing project. Since we technically also generate components, we should respect the default option value for those options if _not_ explicitly specified. Closes #11874
What is the current state?
And I got this error. What is the official solution? |
Hi there, In Angular v8, I'm still facing this problem. To be noted : I have more than 1 application in my Angular project. I have my initial application in 'src' folder, and the others are in the 'project' folder. When I do: I tried to change the
By default, in my
So, it should take into account my default preferences for the whole project, right ? |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Bug, feature request, or proposal:
BUG
What is the expected behavior?
When I've configured the CLI to use scss and skip tests for generated components, I would expect the material schematics to use already defined configuration when generating components (such as the dashboard).
What is the current behavior?
When I try to create material-dashboard it is created with .css instead of .scss and with .spec file
What are the steps to reproduce?
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Is there anything else we should know?
I see that command "ng add @angular/material" add only theme file in angular.json
May be that command has to add schematic too?
The text was updated successfully, but these errors were encountered: