humanmade / humanmade/linter-bot

Add ability to use versions from composer.json and package.json

Open
#145 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
JavaScript
Stars
16
Forks
2
Avg merge
17d 47m
Merged PRs (30d)
1

Description

In [the Configuration section of the readme](https://github.com/humanmade/linter-bot#configuration) it's documented that the version for HM Coding Standards, phpcs, eslint, and stylelint can all be configured.

When I'm using a project that already specifies these versions in composer.json and package.json, I don't want to specify them again here and risk that the versions diverge. This can result in one of the most frustrating types of problems with linting which is when one linting tool displays an error and another doesn't.

It should be possible to instruct linter bot to use the version from these files. An example `hmlinter.yml` using a mixture of config could look like this:

```yaml
# GLOBAL SETTINGS

version: 1.1.1

# PER-STANDARD SETTINGS
phpcs:
enabled: true
version: composer.json

eslint:
enabled: true
version: package.json

stylelint:
enabled: true
version: 13.7.2
```

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.