Skip to content
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.

Sign up for GitHub

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

Jump to bottom

scss-lint developers suggest using new linter #278

Open
UnsolvedCypher opened this issue Dec 4, 2018 · 0 comments
Open

scss-lint developers suggest using new linter #278

UnsolvedCypher opened this issue Dec 4, 2018 · 0 comments

Comments

@UnsolvedCypher
Copy link

Because Ruby Sass is being deprecated, and the developers suggest moving to stylelint or sass-lint. It would be great to include one or both of these linters since projects are likely to slowly move away from scss-lint.
@UnsolvedCypher UnsolvedCypher mentioned this issue Dec 4, 2018
Closed
jfly added a commit to jfly/worldcubeassociation.org that referenced this issue Jul 30, 2019
@jfly
Switch from using the pre_commit gem to overcommit
c6ad92b 
`pre_commit` was starting to show its age:
  - It uses the now defunct `scss-lint` package. See
    jish/pre-commit#278 and
    thewca#3649.
  - It bundles an older version of JsHint that does not have support
    for ES{7,8,9}.

I've configured `overcommit` to behave similarly to `pre_commit`. Here's
a list of the specific things I've configured and tested:

    + css linting using stylelint (this brings us one step closer to
      getting off of `ruby-sass`:
      thewca#3649)
    + illegal char check (such as <<<)
    + rubocop
    + jshint (with support for ES9!)
jfly added a commit to jfly/worldcubeassociation.org that referenced this issue Jul 30, 2019
@jfly
Switch from using the pre_commit gem to overcommit
6db41e5 
`pre_commit` was starting to show its age:
  - It uses the now defunct `scss-lint` package. See
    jish/pre-commit#278 and
    thewca#3649.
  - It bundles an older version of JsHint that does not have support
    for ES{7,8,9}.

I've configured `overcommit` to behave similarly to `pre_commit`. Here's
a list of the specific things I've configured and tested:

    + css linting using stylelint (this brings us one step closer to
      getting off of `ruby-sass`:
      thewca#3649)
    + illegal char check (such as <<<)
    + rubocop
    + jshint (with support for ES9!)
jfly added a commit to jfly/worldcubeassociation.org that referenced this issue Jul 30, 2019
@jfly
Switch from using the pre_commit gem to overcommit
229e3d1 
`pre_commit` was starting to show its age:
  - It uses the now defunct `scss-lint` package. See
    jish/pre-commit#278 and
    thewca#3649.
  - It bundles an older version of JsHint that does not have support
    for ES{7,8,9}.

I've configured `overcommit` to behave similarly to `pre_commit`. Here's
a list of the specific things I've configured and tested:

    + css linting using stylelint (this brings us one step closer to
      getting off of `ruby-sass`:
      thewca#3649)
    + illegal char check (such as <<<)
    + rubocop
    + jshint (with support for ES9!)
jfly added a commit to jfly/worldcubeassociation.org that referenced this issue Jul 30, 2019
@jfly
Switch from using the pre_commit gem to overcommit
ad3787b 
`pre_commit` was starting to show its age:
  - It uses the now defunct `scss-lint` package. See
    jish/pre-commit#278 and
    thewca#3649.
  - It bundles an older version of JsHint that does not have support
    for ES{7,8,9}.

I've configured `overcommit` to behave similarly to `pre_commit`. Here's
a list of the specific things I've configured and tested:

    + css linting using stylelint (this brings us one step closer to
      getting off of `ruby-sass`:
      thewca#3649)
    + illegal char check (such as <<<)
    + rubocop
    + jshint (with support for ES9!)
jfly added a commit to jfly/worldcubeassociation.org that referenced this issue Jul 30, 2019
@jfly
Switch from using the pre_commit gem to overcommit
df79099 
`pre_commit` was starting to show its age:
  - It uses the now defunct `scss-lint` package. See
    jish/pre-commit#278 and
    thewca#3649.
  - It bundles an older version of JsHint that does not have support
    for ES{7,8,9}.

I've configured `overcommit` to behave similarly to `pre_commit`. Here's
a list of the specific things I've configured and tested:

    + css linting using stylelint (this brings us one step closer to
      getting off of `ruby-sass`:
      thewca#3649)
    + illegal char check (such as <<<)
    + rubocop
    + jshint (with support for ES9!)
jfly added a commit to jfly/worldcubeassociation.org that referenced this issue Jul 30, 2019
@jfly
Switch from using the pre_commit gem to overcommit
70adecc 
`pre_commit` was starting to show its age:
  - It uses the now defunct `scss-lint` package. See
    jish/pre-commit#278 and
    thewca#3649.
  - It bundles an older version of JsHint that does not have support
    for ES{7,8,9}.

I've configured `overcommit` to behave similarly to `pre_commit`. Here's
a list of the specific things I've configured and tested:

    + css linting using stylelint (this brings us one step closer to
      getting off of `ruby-sass`:
      thewca#3649)
    + illegal char check (such as <<<)
    + rubocop
    + jshint (with support for ES9!)
jfly added a commit to thewca/worldcubeassociation.org that referenced this issue Jul 31, 2019
@jfly
Switch from using the pre_commit gem to overcommit
cf1b6f4 
`pre_commit` was starting to show its age:
  - It uses the now defunct `scss-lint` package. See
    jish/pre-commit#278 and
    #3649.
  - It bundles an older version of JsHint that does not have support
    for ES{7,8,9}.

I've configured `overcommit` to behave similarly to `pre_commit`. Here's
a list of the specific things I've configured and tested:

    + css linting using stylelint (this brings us one step closer to
      getting off of `ruby-sass`:
      #3649)
    + illegal char check (such as <<<)
    + rubocop
    + jshint (with support for ES9!)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@UnsolvedCypher