Skip to content

fix: generate style with right extension for default project #14527

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

Closed
wants to merge 1 commit into from

Conversation

tiaguinho
Copy link
Contributor

Closes #14309

@tiaguinho tiaguinho force-pushed the master branch 2 times, most recently from aaca95e to 8bc69b5 Compare May 31, 2019 06:14
@clydin
Copy link
Member

clydin commented Aug 13, 2019

Thank you for the contribution.
However, the referenced issue is no longer present in the latest version of the CLI.

@clydin clydin closed this Aug 13, 2019
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 13, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

CLI does not respect style file extension set in schematic when generating components without specifying the project
4 participants