[wp-trac] [WordPress Trac] #47434: Consider updating CSSLint manually
WordPress Trac
noreply at wordpress.org
Thu Sep 26 21:11:43 UTC 2019
#47434: Consider updating CSSLint manually
--------------------------------+------------------------------
Reporter: vedjain | Owner: (none)
Type: feature request | Status: new
Priority: normal | Milestone: Awaiting Review
Component: External Libraries | Version:
Severity: minor | Resolution:
Keywords: needs-patch early | Focuses:
--------------------------------+------------------------------
Changes (by desrosj):
* keywords: => needs-patch early
Comment:
Hi @vedjain!
Welcome to Trac! My apologies that it took a while to receive a response.
While updating external libraries separately from a library versioned
release is sometimes done, reaching out to the maintainers for CSSLint and
working with them to release a new version is the much preferred option.
Especially where there are 24 commits since the last release and not just
one or two changes
([https://github.com/CSSLint/csslint/compare/v1.0.3...master full change
log since 1.0.3]).
Looking at the CSSLint repository, there has also only been one commit in
the last year, and a few more than 3 in the last 2 years. Another approach
would be to see if there are better maintained more modern alternatives to
CSSLint that could be looked at. For this option, all use within WordPress
Core would need to be documented.
I'm also marking this as an `early` ticket. When the library is updated,
it's preferable to do so early on in the release cycle to ensure proper
testing occurs.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/47434#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list