Add workaround for PostCSS parse error #19460
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Hi @mshibuya ! Thanks for this PR. Unfortunately this cannot be merged becaue there is an upstream repository with the source code. Let's ask @robmadole if by any chance this can be prioritized, since it is an easy, non-breaking fix |
tagliala
approved these changes
Feb 3, 2023
ArthurKoba
approved these changes
Feb 14, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a fix for #18899. I need this to solve the issue RailsAdmin users are facing.
I hope one of Font-Awesome maintainers can apply this to the respective upstream.
I understand that:
I understand that it will not be merged and I will not be listed as a contributor on this project.