-
Notifications
You must be signed in to change notification settings - Fork 313
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Updating CSSLint and CodeMirror #10
Comments
stylellint is a more active and modern alternative to CSSLint. It could potentially be included through Also see stylish-userstyles/stylish-chrome#184 for some more discussion about it. |
CodeMirror and CSSLint are updated to versions 5.23.0 and 1.0.4 on @tophf is there anything else in https://github.com/schomery/stylish-chrome/tree/codemirror-update/codemirror that can be removed? |
Half of the addons you added can be removed I guess. You should have updated only the existing files. See my old PR. |
@tophf all the unnecessary addons are removed; 0e13a15 @narcolepticinsomniac how about now; 0f63da4 |
Much better so far. I see some improvements on false positives as well. Overall it seems a decent improvement. Not sure whether there's any good fixes for Lint's limitations. |
Why CSSLint 1.0.4? It's 1.0.5 in the official repo, the main change being parser 1.1.1 update (see CSSLint/parser-lib@v1.0.0...v1.1.1). |
Everything's fine, their versioning is simply weird: 1.0.4 inside the files but the repo is tagged 1.0.5 just after the dist update :-) |
@narcolepticinsomniac this |
Yeah, like I said, these are "bugs" in CSSLint itself. I don't use variables personally, but a lot of people do. The issue has been brought up for years with no resolution. As for the Variables are more important, and they tend to throw errors. In general, the update is an improvement regardless. These are only a couple shortcomings I observed right off the bat that were always issues and apparently still are. |
This is merged to the master branch |
hex mode similar to chrome-devtools: * Ctrl-Up/Down for R channel * Shift-Up/Down for G channel * Alt-Up/Down for B channel * Up/Down treats the entire color as a hex integer e.g. #00f -> #10 rgb/hsl modes similar to chrome-devtools: * Ctrl-Up/Down steps by 100 (alpha: by 1) * Shift-Up/Down steps by 10 (alpha: by .1) * Up/Down steps by 1 (alpha: by .01) * PgUp/PgDn to switch format * Tab to switch format when at the first/last input field
hex mode similar to chrome-devtools: * Ctrl-Up/Down for R channel * Shift-Up/Down for G channel * Alt-Up/Down for B channel * Up/Down treats the entire color as a hex integer e.g. #00f -> #10 rgb/hsl modes similar to chrome-devtools: * Ctrl-Up/Down steps by 100 (alpha: by 1) * Shift-Up/Down steps by 10 (alpha: by .1) * Up/Down steps by 1 (alpha: by .01) * PgUp/PgDn to switch format * Tab to switch format when at the first/last input field
#5 (comment)
The text was updated successfully, but these errors were encountered: