tonyair/silverstripe-framework
1
0
Fork 0
mirror of https://github.com/silverstripe/silverstripe-framework synced 2024-09-30 05:09:06 +02:00
Code Issues Projects Releases Wiki Activity

Updated docs with sass-lint references

Browse Source
This commit is contained in:
Ingo Schommer 2016-09-18 16:25:16 +12:00
parent 96892636c7
commit a0c0a4ae4f
2 changed files with 8 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/en/05_Contributing/02_Build_Tooling.md
View File

@ -99,7 +99,9 @@ $ npm run css -- --watch
$ npm run lint
```
Run `eslint` over JavaScript files reports errors.
Run linters (`eslint` and `sass-lint`) linters to enforce
our [JavaScript](/contributing/javascript_coding_conventions) and
[CSS](/contributing/css_coding_conventions) coding conventions.
### test

7
docs/en/05_Contributing/13_CSS_Coding_Conventions.md
View File

@ -29,9 +29,12 @@ File naming and style include ordering is inspired by
We use [sass-lint](hhttps://github.com/sasstools/sass-lint) to ensure all new SCSS
written complies with the rules below. It will be provided as an npm dev dependency.
Ther eare also quite a few [sass-lint IDE integrations]https://github.com/sasstools/sass-lint#ide-integration) which highlight any linting errors right in your code.
Ther eare also quite a few [sass-lint IDE integrations]https://github.com/sasstools/sass-lint#ide-integration)
which highlight any linting errors right in your code.
We strongly recommend installing one of these into the editor of your choice, to
avoid the frustration of failed pull requests.
avoid the frustration of failed pull requests. You can run the checks on console
via `npm run lint`.
## File and Folder Naming