-
-
Notifications
You must be signed in to change notification settings - Fork 833
Conversation
Signed-off-by: Suguru Hirahara <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What are those warnings and why does PostCSS spit them out?
I'm not convinced this is the right fix. I have a hunch this happens because of outdated packages
Using justify-content: start
is completely valid in this instance and I would not want to change our code to satisfy this tool's incorrect expectations
Essentially the same PR as #9500. As I myself am not annoyed with these warnings, it's ok for me to close this. What do you think? |
I understand what you're getting at, I'm just not sure this is how we should approach it. |
Might be reopened after element-hq/element-web#23597 is resolved. |
Signed-off-by: Suguru Hirahara [email protected]
This change stops webpack from issuing warnings related to
justify-content: start
. See: element-hq/element-web#23595type: task
Checklist
This change is marked as an internal change (Task), so will not be included in the changelog.