Skip to content

fix(@angular/cli): support inlining stylesheet resource tilde paths #8791

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

Merged
merged 1 commit into from
Dec 21, 2017

Conversation

clydin
Copy link
Member

@clydin clydin commented Dec 7, 2017

Fixes #8781

@tamascsaba
Copy link

@filipesilva pls review and merge. I will be very happy :) it is very cool functionality in my app,

@ghost
Copy link

ghost commented Dec 19, 2017

@filipesilva pls...

@filipesilva filipesilva merged commit 9caa7ca into angular:master Dec 21, 2017
@clydin clydin deleted the no-tilde-inline branch December 21, 2017 13:11
@kaloczidev
Copy link

Thank you!

douglasduteil added a commit to douglasduteil/angular-cli that referenced this pull request Jan 4, 2018
Ensure that, on Windows, the path doesn't contain back slashes to be PostCSS friendly :)

Following angular#8791 
Closes angular#9077 angular#9061 angular#9080
douglasduteil added a commit to douglasduteil/angular-cli that referenced this pull request Jan 4, 2018
Ensure that, on Windows, the path doesn't contain back slashes to be PostCSS friendly :)

Following angular#8791
Closes angular#9077 angular#9061 angular#9080
@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 12, 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.

Postcss warnings with ~ font paths relative to node_modules after upgrading from 1.5.0 to 1.6.0
5 participants