You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
#550's coding-standards criterion is unchecked partly because nothing lints the CSS, while @wordpress/scripts already ships stylelint with WordPress's config, so a lint:css script and a CI step are all it takes.
Running it on the stylesheets today finds one problem:
$ npx wp-scripts lint-style "plugins/presence-api/assets/css/*.css"
plugins/presence-api/assets/css/stale-screen.css
15:2 ✖ Expected empty line before comment comment-empty-line-before
Tasks
lint:css in package.json, running wp-scripts lint-style on plugins/presence-api/assets/css/
Fix the one problem above
Run it in CI beside lint:js
Decide whether the inline CSS in post-list.php, admin-bar.php and the two widget classes moves into stylesheets so it is linted too, or stays inline and unlinted
I'd propose to move it into stylesheets. The four blocks in admin-bar.php, post-list.php and the two widget classes are plain strings with nothing dynamic in them, so they can go into assets/css/ unchanged and get picked up by lint:css.
Activity
i-am-chitti commentedon Oct 12, 2026
@josephfusco @huzaifaalmesbah #811 covered everything here except the inline CSS question.
I'd propose to move it into stylesheets. The four blocks in
admin-bar.php,post-list.phpand the two widget classes are plain strings with nothing dynamic in them, so they can go intoassets/css/unchanged and get picked up bylint:css.josephfusco commentedon Oct 12, 2026
Agreed, move the four blocks into
assets/css/solint:csspicks them up.[-]The CSS is not linted[/-][+]The inline CSS in PHP files is not linted[/+]i-am-chitti commentedon Oct 12, 2026
I'm picking this up and moving inline CSS to stylesheets.