Code Monkey home page Code Monkey logo

stylelint-config-sass-guidelines's Introduction

stylelint-config-sass-guidelines

NPM version Build Status Known Vulnerabilities contributions welcome Downloads per month

A stylelint config inspired by sass-guidelin.es.

This linter has been designed / tested with SCSS syntax based on the SCSS guidelines documented in https://sass-guidelin.es/. It is intended for use with SCSS syntax, not Sass (tab style) syntax.

This config:

Translations

Installation

$ npm i -D stylelint postcss stylelint-config-sass-guidelines

Usage

Set your stylelint config to:

{
  "extends": "stylelint-config-sass-guidelines"
}

Extending the config

Simply add a "rules" key to your config and add your overrides there.

For example:

{
  "extends": "stylelint-config-sass-guidelines",
  "rules": {
    "selector-max-compound-selectors": 4,
    "value-no-vendor-prefix": false
  }
}

Documentation

Configured lints

This is a list of the lints turned on in this configuration, and what they do.

At-rule

Block

Color

Declaration block

Declaration Property

  • declaration-property-value-disallowed-list: Specify a list of disallowed property and value pairs within declarations.
    • ^border: Disallow the use of the word none for borders, use 0 instead. The intent of this rule is to enforce consistency, rather than define which is "better."

Function

General

Media Feature

Property

Rule

SCSS

Selector

Value

Contributors

stylelint-config-sass-guidelines is maintained by Brett Jankord and contributions from the community. Without the code contributions from all these fantastic people, stylelint-config-sass-guidelines would not exist.

stylelint-config-sass-guidelines's People

Contributors

bjankord avatar bouzlibop avatar dbartholomae avatar dependabot-preview[bot] avatar dependabot[bot] avatar frinyvonnick avatar gfyoung avatar greenkeeper[bot] avatar haberkamp avatar hyzual avatar leocolomb avatar rmcveigh avatar snyk-bot avatar stof avatar stormwarning avatar tristanbes avatar vincentducorps avatar xi avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

stylelint-config-sass-guidelines's Issues

Broken link

It appears that the top link in this section of the readme is broken.

Add engines entry into package.json to denote project requires node 6 or above similar to stylelint.

With stylelint v9, they removed Node.JS 4.x support. Node.js 6.x or greater is now required.

stylelint includes a package entry for engines to denote it requires node v6 or above

"engines": {
    "node": ">=6"
  },

I'm planning on doing the same for this package. While I'm unsure if anyone is using Node.JS < 6.x with this package, this would be breaking change for those users. This change will then trigger a new major release, stylelint-config-sass-guidelines v5 once it is ready to be released. For users on Node.JS 6.x or above, they should notice no change in behavior or functionality.

Is this compatible with stylelint-config-standard?

Am I able to use both configs as such:

{
  "extends": [
    "stylelint-config-standard",
    "stylelint-config-sass-guidelines"
  ]
}

And if so, which should come first?
If this is the case, it might be useful information for the README, I'd be willing to PR it.

Declaration block properties order Rule

Hi,

I found something to clarify

Regarding

declaration-block-properties-order: Properties in declaration blocks must be sorted alphabetically.

Based on the page, the author didn't impose preference regarding property order

image

I wonder if it is better to remove the Rule to follow what the doc said?

However, In the .stylelint.rc I could do this to ignore the rule

{
"extends": "stylelint-config-sass-guidelines",
"rules": {
    "order/properties-alphabetical-order": null
  }
}

Stylelint v10

Hello.
Stylelint v10 was released long time ago and I can't see any issues except getting the warinig:
warning "stylelint-config-sass-guidelines > [email protected]" has incorrect peer dependency "stylelint@^8.0.0 || ^9.0.0".

Could be the library dependency to be allowed also for ^10.0.0, please?

selector-class-pattern fails on selectors with more than 2 dashes

Hi,

I've experienced this issue when I wrote a selector that includes more than 2 dashes

.drop-open-transitionend {
   display: block;
}

Selector should be written in lowercase with hyphens. selector-class-pattern.

If I wrote it as follows

.drop-open {
   &-transitionend {
      display: block;
   }
}

It just works.

Is it the intended behavior ?

Disable declaration-block-properties-alphabetical-order

Hey is it possible to disable the declaration-block-properties-alphabetical-order I currently have:

"order/declaration-block-properties-alphabetical-order": false

Which works but gives the following error:

Invalid Option: Unexpected option value "false" for rule "order/declaration-block-properties-alphabetical-order"

Was hoping there was a native way to do this?

Cheers.

TypeError: Class extends value undefined is not a constructor or null at Object.<anonymous> - PostCSS < v8 + Stylelint v14 compat issue

This issue seems to happen with the v9.0.0 release of stylelint-config-sass-guidelines and is related to stylelint v14 release.
In stylelint v14.0.0, the syntax option and automatic inferral of syntax was removed.

Prior to stylelint v14.0.0, stylelint was able to parse CSS-like languages like SCSS without extra dependencies. Now they recommend using postcss-scss in your stylelint config via "customSyntax": "postcss-scss",

The customSyntax": "postcss-scss" syntax was recently added to this config in this PR to update this config to use stylelint v14.

Currently, postcss-scss has a peer dependency on postcss v8.3.3:
https://github.com/postcss/postcss-scss/blob/main/package.json#L35-L37

Peer dependencies can typically be interpreted as the project that uses postcss-scss should pull in v8.3.3 version of postcss on their own as postcss-scss is dependent on it.

When reviewing the PR for the update this config to stylelint v14, the dependency tree had postcss v8 via transitive dependencies. The unit tests and manual tests passed and stylelint ran successfully on this project's SCSS files.

I noticed this TypeError issue in another project that uses stylelint-config-sass-guidelines when updating it to v9.0.0.
The dependency tree in the project currently uses postcss v7.

Running the following npm script "stylelint": "stylelint '**/*.scss'" in the project that used
[email protected] and had postcss v7 in it's dependency tree resulted in the error TypeError: Class extends value undefined is not a constructor or null at Object.<anonymous>

My understanding is if your dependency tree uses a version of postcss less than v8, you'll likely see the following error when running stylelint with this [email protected] config:

TypeError: Class extends value undefined is not a constructor or null  at Object.<anonymous>
(/Users/username/repos/open-source/project-name/node_modules/postcss-scss/lib/nested-declaration.js:3:33)

Missing `ruleName`

I got the following error in VS Code after enabling the plugin:

stylelint: stylelint v3+ requires plugins to expose a ruleName. The plugin ".../node_modules/stylelint-config-sass-guidelines/index.js" is not doing this, so will not work with stylelint v3+. Please file an issue with the plugin.

An in-range update of stylelint-scss is breaking the build 🚨

The dependency stylelint-scss was updated from 3.3.2 to 3.4.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

stylelint-scss is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

Commits

The new version differs by 13 commits.

  • 8cb1656 Prepare version 3.4.0
  • baa0e66 Merge pull request #283 from kristerkari/bugfix/correctly-handle-parameters-in-partial-no-import
  • 2089d5f fix typo [ci skip]
  • e2f9e64 Add test
  • 17a5941 partial-no-import: correctly handle import parameters with urls
  • 885fefd Merge pull request #280 from niksy/at-mixin-argumentless-call-parentheses-fix
  • 4fdc378 Add "at-mixin-argumentless-call-parentheses" autofix
  • 921b294 Merge pull request #281 from kristerkari/feat/dependencies-bump
  • d298945 Update dependencies to latest versions
  • ec91b1c remove unused npm script
  • ad53965 Use eslint-plugin-lodash to avoid possible errors with Lodash
  • 2baa882 make contributor avatars bigger
  • f9650f8 Add a list of contributors

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of stylelint-scss is breaking the build 🚨

The dependency stylelint-scss was updated from 3.13.0 to 3.14.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

stylelint-scss is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • Node 12 on ubuntu-latest: null
  • Node 10 on ubuntu-latest: null
  • Node 8.16.2 on ubuntu-latest: null

Release Notes for 3.14.0
  • Added: support for stylelint version 13.
  • Fixed: avoid possible breaking changes in the future by not using stylelint's internal utility functions.
Commits

The new version differs by 21 commits.

  • e005ff5 Prepare version 3.14.0 [skip ci]
  • 801cc98 Update contributors list [skip ci]
  • fd2922e Merge pull request #437 from kristerkari/lodash
  • 2d48896 Switch back to using the lodash package.
  • 4ea73e7 Merge pull request #428 from kristerkari/stylelint-13
  • 1445870 Add new upstream files for Stylelint v13.0.0 compatibility.
  • aa2e809 Update stylelint to v13.0.0
  • d23e3d7 Merge pull request #435 from kristerkari/stylelint-api
  • c2a0a60 Merge pull request #446 from kristerkari/deps-2
  • 01e8806 Update devDependencies
  • 34afdcc Update devDepencies. (#444)
  • f2c7cf0 Remove eslint-plugin-sort-requires (#436)
  • fb6c418 Fix typo in comment
  • 0905db6 Stop using private Stylelint code
  • ba1fa12 Merge pull request #427 from kristerkari/deps

There are 21 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of stylelint is breaking the build 🚨

Version 9.4.0 of stylelint was just published.

Branch Build failing 🚨
Dependency stylelint
Current Version 9.3.0
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

stylelint is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Release Notes 9.4.0
  • Added: bundled support for styles in template literals (#3405).
  • Added: linebreaks rule (#3289).
  • Added: compact formatter (#3488).
  • Added: at-rule-semicolon-newline-after autofix (#3450).
  • Added: block-closing-brace-newline-after autofix (#3443).
  • Added: block-opening-brace-space-before autofix (#3438).
  • Added: declaration-block-trailing-semicolon autofix (#3382).
  • Added: declaration-colon-space-before autofix (#3445).
  • Added: property-case autofix (#3448).
  • Added: selector-combinator-space-after autofix (#3446).
  • Added: selector-combinator-space-before autofix (#3457).
  • Added: selector-list-comma-space-before autofix (#3447).
  • Fixed: block-opening-brace-newline-after false positives for nested rule-sets prefixed with comments (#3383).
  • Fixed: declaration-block-trailing-semicolon report of errors with the --fix option (#3493).
  • Fixed: font-family-name-quotes false positives for system-ui system font (#3463).
  • Fixed: keyframes-name-pattern support for raw JS RegExp (#3437).
  • Fixed: media-feature-name-no-unknown false positives for level 5 names (#3397).
  • Fixed: no-descending-specificity false positives for #{&} (#3420).
  • Fixed: no-missing-end-of-source-newline false positives for style attributes (#3485).
Commits

The new version differs by 67 commits.

  • 5c789fd Update CHANGELOG.md
  • f7edb36 Fix reports of errors with the --fix option in declaration-block-trailing-semicolon
  • 148c09f Typo (#3497)
  • 7340df1 Tweak README (#3496)
  • 4b868f3 Prepare 9.4.0
  • faef7cc Prepare CHANGELOG
  • 093e021 Remove unused error option from --rd docs (#3495)
  • 002619d Simplify README structure and language (#3491)
  • 35a24b8 Use "ID" and not "id" throughout (#3486)
  • 824b895 Update CHANGELOG.md
  • 700b7fb Add a "compact" formatter (#3488)
  • b07e9c8 Fix inconsistent linebreaks docs (#3489)
  • acec955 Update CHANGELOG.md
  • 8e28932 Add autofix to block-closing-brace-newline-after (#3443)
  • db49361 Update CHANGELOG.md

There are 67 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

stylelint: Undefined rule at-rule-disallowed-list error in VSCode

When using this config, it appears while editing SCSS in VScode, a prompt shows up about Undefined rule at-rule-disallowed-list error in VSCode.

Currently this is only used to disable the @debug rule in SCSS files but I may look into removing this rule altogether if I cannot find a better solution.
Screen Shot 2021-02-11 at 8 27 41 AM

An in-range update of stylelint-order is breaking the build 🚨

The dependency stylelint-order was updated from 3.1.0 to 3.1.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

stylelint-order is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

Release Notes for 3.1.1
  • Added stylelint@11 as a peer dependency.

3.1.0...3.1.1

Commits

The new version differs by 3 commits.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Warning occurring on all sass files: Unknown rule declaration-property-value-disallowed-list , Unknown rule at-rule-disallowed-list

Screenshot_20201109_153459

This is my .stylelintrc.js configuration:

module.exports = {
  extends: [
    "stylelint-config-standard",
    "stylelint-config-sass-guidelines",
    "stylelint-config-prettier",
  ],
  plugins: [
    "stylelint-scss",
    "stylelint-order",
  ],
  ignoreFiles: ["dist/**"],
  rules: {
    "at-rule-no-unknown": null,
    "scss/at-rule-no-unknown": true,
    "at-rule-disallowed-list": [],
    "declaration-property-value-disallowed-list": {},
  },
};

@bjankord is there any way to disable these last two rules? In my config above I tried setting them to null, false, and assigning empty array/object, but to no success. I'm entirely sure why these errors are cropping up.

https://github.com/bjankord/stylelint-config-sass-guidelines/blob/main/index.js#L4

https://github.com/bjankord/stylelint-config-sass-guidelines/blob/main/index.js#L21

As far as ordering goes, I tried switching stylelint-config-sass-guidelines above and below stylelint-config-standard to see if there were any conflicts, but still getting the same result. I tried removing everything except stylelint-config-sass-guidelines and the errors are still present.

border none: explanation

Howdy, I'm trying to get to the bottom of why border:none is specifically disallowed:
https://github.com/bjankord/stylelint-config-sass-guidelines/blob/master/src/.stylelintrc.json#L21

I see that this is based on sass guidelines, but the Sass Guidelines never recommend border: 0 over border: none explicitly.

The Sass Guidelines are based on CSS Guidelines, but Harry Roberts never recommends this rule.

The Sass Guidelines are also following SCSS lint, and SCSS Lint has this rule for border:0, but it, too, never explains why.

SCSS-Lint has multiple examples of specifically surfacing an error for border: none but without explanation.

So I'm making the rounds trying to determine why this rule exists and what benefit it serves. Could you provide an explanation?

Ignore @each for max-nesting-depth

Hi there,

the max-nesting-depth rule currently doesn't ignore @each at the moment, which makes this code fail linting:

.button {
  // Button colors
  @each $key, $value in $colors {
    &__button--#{$key} {
      background-color: $value;
    }
  }
}

It would be great to modify the rule to allow for this kind of code as it is in line with the Sass Guidelines:

    "max-nesting-depth": [
      1,
      {
        "ignoreAtRules": [
          "media",
          "supports",
          "include",
          "each"
        ]
      }
    ]

If there's interest, I'll create the PR.

PostCSS Upgrade

Hello it seems like today a security vulnerability for PostCSS v7 has been discovered and it looks like it has been resolved in v8.2.10. Is there any plans to update the dependency to a safe version?

Screen Shot 2021-05-10 at 4 43 14 PM

Extending "stylelint-config-sass-guidelines" leads to fatal error

As mentioned here: stylelint-scss/stylelint-scss#266 (comment)

One of the rules defined in your config creates stylelint to fatally crash due tue JS memory allocation:

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory

It is all based on this rule:
https://github.com/bjankord/stylelint-config-sass-guidelines/blob/master/src/.stylelintrc.json#L90
"scss/percent-placeholder-pattern": "^[a-z]+([a-z0-9-]+[a-z0-9]+)?$",

I copied all your config directly into my .stylelintrc except this one rule and everything was fine.

Maybe you can fix it by just upgrading your dependencies of stylelint-scss

Thanks!

Removing stylelint-order

I must say I cannot decide myself. A recent poll on CSS-Tricks determined that over 45% developers order their declarations by type against 14% alphabetically. Also, there are 39% that go full random, including myself.
[...]
Because of this, I will not impose a choice in this styleguide. Pick the one you prefer, as long as you are consistent throughout your stylesheets (i.e. not the random option).
§ Declaration Sorting

The guidelines specifically leave this question undecided. In any case, a user can always install it manually.

export stylelintrc.json

There is no need to maintain 2 configurations at the same time. We can directly export the src/.stylelintrc.json from package.json.
This will remove build script, shelljs as dependency.

Deprecation warnings

Hi,

There are four deprecation warnings in this configuration that won't be supported in the next major release of stylelint:

Deprecation Warning: 'declaration-block-properties-order'has been deprecated and in 8.0 will be removed. Instead use the community 'stylelint-order' plugin pack. See: https://stylelint.io/user-guide/rules/declaration-block-properties-order/
Deprecation Warning: 'rule-nested-empty-line-before' has been deprecated and in 8.0 will be removed. Instead use 'rule-empty-line-before'. See: https://stylelint.io/user-guide/rules/rule-nested-empty-line-before/
Deprecation Warning: 'rule-non-nested-empty-line-before' has been deprecated and in 8.0 will be removed. Instead use 'rule-empty-line-before'. See: https://stylelint.io/user-guide/rules/rule-non-nested-empty-line-before/
Deprecation Warning: 'stylelint-disable-reason' has been deprecated and in 8.0 will be removed. See: https://stylelint.io/user-guide/rules/stylelint-disable-reason/

disable / change property order

I would like to disable or change the order of properties, but can't figure out how. The link to the 'declaration-block-properties-order' does not work.

I tried this to disable, neither works:
rules: { 'declaration-block-properties-order': null, 'properties-alphabetical-order': null, }

Being able to change the order form alphabetic to idiomatic would also be ok.

would love to get some help with this!

border-image: none; produce an error

As for now there is this rule defined:

    "declaration-property-value-blacklist": {
      "/^border/": [
        "none"
      ]
    },

If I want to define something like this:
border-image: none;
it will produce an error because of the above mentioned rule.

I'm curious why stylelint-config-sass-guidelines disallow it?

Could not find "stylelint-order"

I get the following error when I enable stylelint-config-sass-guidelines in .stylelintrc from stylelint CLI and Atom.

Error: Could not find "stylelint-order". Do you need a `configBasedir`?

Could not find "stylelint-order". Do you need a configBasedir?

Is there a solution?

Order `dollar-variables` should always come first

For SCSS users, sometimes we need to assign custom CSS properties to SCSS variables, which requires those variables be defined before custom properties are. But with the current ordering, this is impossible.

div {
  $color: blue;

  // Throws an error saying this should be placed above $color.
  --theme-color: #{$color};
}

Can we swap the ordering here of custom-properties and dollar-variables so that variables always come first and before all others?

e.g.

    "order/order": [
      [
        "dollar-variables",
        "custom-properties",
        ...

Version 3.0.0 or 2.0.0 ?

Hi,
Thanks for having updated your package, but obviously you released a 3.0.0 on npm, and your release tag is named v2.0.0 ;).

Ignore all @-rules in max-nesting-depth

#33 was an issue about ignoring @each in "max-nesting-depth". But what about @if, @for, @while, @function, …? The guidelines only talk about selector nesting so I see no reason not to ignore all @-rules.

Version 10 of node.js has been released

Version 10 of Node.js (code name Dubnium) has been released! 🎊

To see what happens to your code in Node.js 10, Greenkeeper has created a branch with the following changes:

  • Added the new Node.js version to your .travis.yml
  • The new Node.js version is in-range for the engines in 1 of your package.json files, so that was left alone

If you’re interested in upgrading this repo to Node.js 10, you can open a PR with these changes. Please note that this issue is just intended as a friendly reminder and the PR as a possible starting point for getting your code running on Node.js 10.

More information on this issue

Greenkeeper has checked the engines key in any package.json file, the .nvmrc file, and the .travis.yml file, if present.

  • engines was only updated if it defined a single version, not a range.
  • .nvmrc was updated to Node.js 10
  • .travis.yml was only changed if there was a root-level node_js that didn’t already include Node.js 10, such as node or lts/*. In this case, the new version was appended to the list. We didn’t touch job or matrix configurations because these tend to be quite specific and complex, and it’s difficult to infer what the intentions were.

For many simpler .travis.yml configurations, this PR should suffice as-is, but depending on what you’re doing it may require additional work or may not be applicable at all. We’re also aware that you may have good reasons to not update to Node.js 10, which is why this was sent as an issue and not a pull request. Feel free to delete it without comment, I’m a humble robot and won’t feel rejected 🤖


FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Deprecation warning with stylelint 13.7.0

Stylelint 13.7.0 was just released today, and renames some rules:

Deprecation Warning: 'at-rule-blacklist' has been deprecated. Instead use 'at-rule-disallowed-list'. See: https://github.com/stylelint/stylelint/blob/13.7.0/lib/rules/at-rule-blacklist/README.md
Deprecation Warning: 'declaration-property-value-blacklist' has been deprecated. Instead use 'declaration-property-value-disallowed-list'. See: https://github.com/stylelint/stylelint/blob/13.7.0/lib/rules/declaration-property-value-blacklist/README.md

sass (tabs) style syntax linting not working

Hi there!

I'm trying to set up SASS (tabs style) linting with stylelint-config-sass-guidelines, but it seems like linter do not apply SASS syntax option syntax: 'sass' in webpack config file and continue to check styles as SCSS.

I love SASS syntax for its minimalism and purity. How I should set up SASS linting here?

SASS styles

img-2018-09-29-17-35-21

Linting result

img-2018-09-29-17-26-23

Webpack

img-2018-09-29-17-29-59

.stylelint.yml

---
extends: stylelint-config-sass-guidelines
rules:
  indentation: tab
  number-leading-zero: 

Mixin parameters are formatted like maps

Thank you for this awesome config for stylelint btw. I really needed some perfect settings for formatting my SCSS files.

That said, i'm using Prettier to format using stylelint using this config, but the parameters of mixins are formatted in same fashion as a map.

Expected:

@mixin type-style($style: null, $types: $type-styles, $only-font-size: false, $important: false) {

Actual:

@mixin type-style(
    $style: null,
    $types: $type-styles,
    $only-font-size: false,
    $important: false
) {

Since i know this is a linter, and not formatter i'm hoping im making this issue the right place.

Kind regards
Dennis

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.