Skip to content

[dist] fixed readme for additional best practices #64

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

Merged
merged 1 commit into from
May 1, 2018
Merged

[dist] fixed readme for additional best practices #64

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -79,7 +79,7 @@ The `--fix` option in `eslint` is [**only** available as a CLI option](https://g
}
```

## Additional Suggestions for Best Practices
## Additional Best Practices

This section is a place for additional best practices that may be useful but are not strictly enforced by this styleguide. Have something to add here? Great! [Submit a PR](#how-do-i-contribute).

Expand All @@ -92,6 +92,7 @@ This section is a place for additional best practices that may be useful but are
### How do I override a specific rule ?

##### 1. Add a `.eslintrc` file at the root of your project:

``` js
{
"extends": "godaddy",
Expand All @@ -103,6 +104,7 @@ This section is a place for additional best practices that may be useful but are
```

##### 2. Add a param to specify the path of your own `.eslintrc` file in your `package.json`:

``` js
{
"scripts": {
Expand Down