respect rule declaration-colon-newline-after
See original GitHub issueoriginal css
background: url(http://webapi.amap.com/theme/v1.3/images/newpc/poi-1.png) no-repeat;
formated css
background: url(http://webapi.amap.com/theme/v1.3/images/newpc/poi-1.png)
no-repeat;
the formatted css does not respect the rule declaration-colon-newline-after: always-multi-line from stylelint-config-standard

Issue Analytics
- State:
- Created 6 years ago
- Reactions:8
- Comments:7
Top Results From Across the Web
declaration-colon-newline-after - Stylelint
There must always be a newline after the colon if the declaration's value is multi-line. The following patterns are considered problems: a {...
Read more >Configuration · Scalafmt - Scalameta
The difference is, the rule forces a newline before a matching assignment expression whether or not it can be formatted on a single...
Read more >GNU make
If the makefiles specify a double-colon rule to remake a file with a recipe but no prerequisites, that file will always be remade...
Read more >Google C++ Style Guide
Tabs; Function Declarations and Definitions; Lambda Expressions ... The following rules will guide you through the various pitfalls of using header files.
Read more >config.txt
Default: auto newlines = auto # lf/crlf/cr/auto # The original size of tabs in ... space after the colon in immutable dictionary expression...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

@zyy7259 umm… It may be a temporary solution but I am looking for a way to make it works instead of just turn it off. Let see if others working on it or not … 😦
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.