All Projects β†’ fsblemos β†’ lint-sass-vue

fsblemos / lint-sass-vue

Licence: other
Atom linter for Vue.js

Programming Languages

coffeescript
4710 projects
javascript
184084 projects - #8 most used programming language

Projects that are alternatives of or similar to lint-sass-vue

linter-alex
πŸ“Sensitive, considerate writing before you merge your Pull Requests
Stars: ✭ 67 (+252.63%)
Mutual labels:  linter
stein
A linter for config files with a customizable rule set
Stars: ✭ 92 (+384.21%)
Mutual labels:  linter
eaf-linter
πŸ€ͺ A linter, prettier, and test suite that does everything as-simple-as-possible.
Stars: ✭ 17 (-10.53%)
Mutual labels:  linter
command line lint
This script generates a report against your command-line history and suggests workflow improvements.
Stars: ✭ 42 (+121.05%)
Mutual labels:  linter
predeclared
Find definitions and declarations in Go source code that shadow predeclared identifiers
Stars: ✭ 26 (+36.84%)
Mutual labels:  linter
golangci-lint
Fast linters Runner for Go
Stars: ✭ 11,019 (+57894.74%)
Mutual labels:  linter
li18nt
🌎 Lint your i18n translation files. Detect conflicting properties, duplicates and make it more readable and easier to maintain by formatting it!
Stars: ✭ 29 (+52.63%)
Mutual labels:  linter
SublimePapyrus
A Sublime Text 2 and 3 package for the Papyrus scripting language.
Stars: ✭ 44 (+131.58%)
Mutual labels:  linter
makefiles
No description or website provided.
Stars: ✭ 23 (+21.05%)
Mutual labels:  linter
unindent
Report code that is unnecessarily indented
Stars: ✭ 18 (-5.26%)
Mutual labels:  linter
vscode-write-good
Write Good Linter for Visual Studio Code
Stars: ✭ 58 (+205.26%)
Mutual labels:  linter
tagref
Tagref helps you maintain cross-references in your code.
Stars: ✭ 92 (+384.21%)
Mutual labels:  linter
constyble
CSS complexity linter
Stars: ✭ 92 (+384.21%)
Mutual labels:  linter
linter-elixirc
Atom Linter plugin for ElixirC
Stars: ✭ 14 (-26.32%)
Mutual labels:  linter
rubocop-linter-action
Rubocop Linter Action: A GitHub Action to run Rubocop against your code!
Stars: ✭ 86 (+352.63%)
Mutual labels:  linter
eslint-config
πŸš€ Jetrockets Standarts | ESLint
Stars: ✭ 20 (+5.26%)
Mutual labels:  linter
atom-perl6-editor-tools
A collection of useful Perl 6 editor tools
Stars: ✭ 19 (+0%)
Mutual labels:  linter
branch-name-lint
Lint your branch names
Stars: ✭ 60 (+215.79%)
Mutual labels:  linter
vscode-elixir-credo
VSCode support for Elixir Linter 'Credo'.
Stars: ✭ 20 (+5.26%)
Mutual labels:  linter
elm-review
Analyzes Elm projects, to help find mistakes before your users find them.
Stars: ✭ 195 (+926.32%)
Mutual labels:  linter

This linter plugin is a fork of AtomLinter/linter-sass-lint that provides an interface to sass-lint for Vue.js.

It will parse .vue files with style tags and works for Sass or SCSS:

<template>
<!-- your tamplate here -->
</template>

<script>
  export default {
    props: {
      // ...
    },
  };
</script>

<style lang="scss" scoped>
/* your rules here */
</style>

Plugin installation

apm install lint-sass-vue

.sass-lint.yml

A .sass-lint.yml config file is required for this linter. You can find an example of one here.

If you already have a .sass-lint.yml file, make sure there is the pattern '**/*.vue' in the include property.

By default this plugin will search up the directory tree for this file, you can also specify a path to this config file in the plugin settings or in ~/.atom/config.cson file. Usually you would place this config file in your projects root and keep it under version control too.

You can use the noConfigDisable option to prevent any attempts at linting (and the missing config error messages you will encounter) if a valid config is not found.

By default a config file found in the root of your currently open project will take preference over a config file specified with the configFile option.

Settings

There are three options you can configure either within the plugin or by editing your ~/.atom/config.cson file.

  • noConfigDisable - Enable to prevent any linting if a valid config file (.sass-lint.yml) is not found in the project root.

  • configFile - this is path to a .sass-lint.yml config file, this should only be used if you'd like to specify a global config file rather than rely on a project config file in the root of your project.

  • globalNodePath This is where you can set your global node installation path. Run npm get prefix and paste the result here. This will be where linter-sass-lint will then search for the globally installed version of sass-lint if you choose to enable this with globalSassLint.

  • globalSassLint This allows you to specify that you want to use your globally installed version of sass-lint (npm install -g sass-lint) instead of the version bundled with linter-sass-lint.

  • resolvePathsRelativeToConfig This option allows you to choose to resolve file paths relative to your config file rather than relative to the root of your currently open project.

Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].