Skip to content

Latest commit

 

History

History
59 lines (43 loc) · 2.36 KB

CONTRIBUTING.md

File metadata and controls

59 lines (43 loc) · 2.36 KB

Contributing

Contributions are welcomed, but keep in mind this is eslint config designed specifically for Swellaby codebases so we wil reject any rule changes that conflict with our desired state.

Opening Issues

Click the below links to create a new issue:

Developing

All that is needed to work with this repo is Node.js and your favorite editor or IDE, although we recommend VS Code.

Building

To build and/or work on this project:

Clone the repo, change into the directory where you cloned the directory, and then run the developer setup script

git clone https://github.com/swellaby/eslint-config.git
cd eslint-config 
npm run dev:setup

Submitting changes

Swellaby members should create a branch within the repository, make changes there, and then submit a PR.

Outside contributors should fork the repository, make changes in the fork, and then submit a PR.

Tests

Unit tests are written using Mocha utilizing Mocha's TDD interface.

The tests will be run as part of the npm build script and can also be run directly via the npm test script. The test results will be displayed in the console.

npm test

If you update any of the various eslint configurations, ensure you update the corresponding unit test(s) as well.

Linting

Unsurprisingly, this repo uses eslint for linting the source code. eslint is automatically run when you run the npm build script and when you make a commit. The eslint configuration file (.eslintrc.js) can be found in the root directory.

You can run eslint at any time by executing the npm lint script:

npm run lint

Back to Top