Bump elm-review from 2.7.2 to 2.8.2

[dependabot]

Bumps elm-review from 2.7.2 to 2.8.2.

Release notes

Sourced from elm-review's releases.

v2.8.2

Bug fix: the tests/ folder at the root of the project was not included in the folders to analyze

---

• Re-introduce looking for the tests/ folder at the root a3d3a2e
• Update initial configuration for new-package 9f693e2

jfmengels/node-elm-review@v2.8.1...v2.8.2

Much faster fixes and extract functionality

(A technical mishap caused 2.8.0 to not be publishable, hence why the jump from 2.7.6 to 2.8.1)

Now requires running jfmengels/elm-review v2.10.0.

This release is partially announced by this announcement blog post.

• By using the package's new way of handling fixes, fixes have become much faster
• Introduce --fix-limit=N flag to limit the number of fixes to apply before prompting the user
• Introduce --extract to extract data from the project (needs to be run with --report=json)
• Include the information of how long a rule ran for when running with --benchmark-info
• More tests folders are now included. Before, elm-review looked at the source-directories plus the tests/ folder in the root of the Elm project. Instead, elm-review will now look for a tests/ folder next to every source-directory. This should accommodate projects with multiple Elm subprojects.

---

Commits: jfmengels/node-elm-review@v2.7.6...v2.8.1

• Update changelog 4a7f5e0
• Update snapshots feb2c18
• Require jfmengels/elm-review v2.10.0 or higher 47a0ebf
• Fix crash when handling error 24ba303
• Ignore test-dependencies in elm.json when downloading using --template 5ab1e8a
• Document the extracts in tooling-integration 0e34fdb
• Don't enable computing extracts by default 0d61ec2
• Add missing changelog for 2.7.6 bea2388
• Report an error if fix-limit is not a positive integer 4882b94
• Change order of checks 44bef6e
• Always report extracts 557ab4b
• Add TODOs 9356cc7
• Compute cache of sources once 71977e8
• Have more consistent error handling for spawnElmJsonAsync 51e48af
• Document the --extract flag more 09c1400
• Fix extra lines printed out when fixing but not using --benchmark-info 8b5fecb
• Remove handler of rule-start and rule-end 7af4622
• Make CliCommunication.send take a list of properties 284164f
• Include tests that are stored in sub-folders 126529c
• Separate the line that count the number of fixes and the benchmark results 50c164e
• Add more inclusive terms e8e35c9
• Rename fix-logger to elm-communication 9fba028

... (truncated)

Changelog

Sourced from elm-review's changelog.

[2.8.2] - 2022-11-09

The tests/ folder at the root of the project is now included in the tests folder to look for.

[2.8.0] / [2.8.1] - 2022-11-08

(A technical mishap caused 2.8.0 to not be publishable, so this is technically only 2.8.1)

Now requires running jfmengels/elm-review v2.10.0.

This release is partially announced by this announcement blog post.

• By using the package's new way of handling fixes, fixes have become much faster
• Introduce --fix-limit=N flag to limit the number of fixes to apply before prompting the user
• Introduce --extract to extract data from the project (needs to be run with --report=json)
• Include the information of how long a rule ran for when running with --benchmark-info
• More tests folders are now included. Before, elm-review looked at the source-directories plus the tests/ folder in the root of the Elm project. Instead, elm-review will now look for a tests/ folder next to every source-directory. This should accommodate projects with multiple Elm subprojects.

[2.7.6] - 2022-10-12

Updated the packages created by elm-review new-package to

• use elm-explorations/test v2
• include NoConfusingPrefixOperator in the default ReviewConfig.

[2.7.5] - 2022-09-10

• Fixed an issue where elm-review init --template ... could sometimes crash if the project already had a review configuration
• Updated the GitHub Actions workflow so that the project always runs on the latest LTS version of Node

[2.7.4] - 2022-08-21

• Fixed an issue on Windows where suppressed didn't work #80
• Improved the error message when a source-directory in the review configuration's elm.json is unknown (fixes #79)
• Changed the error message for suppressed error messages to be nicer
• Documented the --no-color flag, and forced colors to be enabled so that elm-review's output stays colored when piped to commands like less
  • Please report an issue if this causes problems for you

[2.7.3] - 2022-07-13

• Bump dependency got to a version that does not contain known security vulnerabilities
• Show dedicated error message when running elm-review --suppress instead of elm-review suppress
• Improved error message when using an unknown flag
• Added colors to the output of elm-review suppress
• Fixed issue where fix proposals were unnecessarily indented

Commits

• baa9372 2.8.2
• a3d3a2e Re-introduce looking for the tests/ folder at the root
• 9f693e2 Update initial configuration for new-package
• 7e8bd41 2.8.1
• 4a7f5e0 Update changelog
• feb2c18 Update snapshots
• 47a0ebf Require jfmengels/elm-review v2.10.0 or higher
• 24ba303 Fix crash when handling error
• 5ab1e8a Ignore test-dependencies in elm.json when downloading using --template
• 0e34fdb Document the extracts in tooling-integration
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Superseded by #16.