Closed dependabot[bot] closed 11 months ago
[!IMPORTANT]
Auto Review Skipped
Bot user detected.
To trigger a single review, invoke the
@coderabbitai review
command.
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?
Updated dependencies detected. Learn more about Socket for GitHub ↗︎
Packages | Version | New capabilities | Transitives | Size | Publisher |
---|---|---|---|---|---|
eslint | 8.37.0...8.56.0 | None | +4/-12 |
4.29 MB | eslintbot |
I'm currently fixing this PR to address the following:
It seems that new dependencies have been added to the package-lock.json file without corresponding unit tests. It is important to have unit tests for all new business logic to ensure code quality and prevent regressions. Please add unit tests for the following dependencies: - @aashutoshrathi/word-wrap@1.2.6 - @eslint-community/regexpp@4.10.0 - @eslint/eslintrc@2.1.4 - @eslint/eslintrc/node_modules/globals@13.24.0 - @eslint/eslintrc/node_modules/type-fest@0.20.2 - @eslint/js@8.56.0 - @humanwhocodes/config-array@0.11.13 - @humanwhocodes/object-schema@2.0.1 - @ungap/structured-clone@1.2.0 - acorn@8.11.3 - acorn-jsx@5.3.2 - ajv@6.12.6 - espree@9.6.1 - eslint-scope@7.2.2 - eslint-visitor-keys@3.4.3 - graphemer@1.4.0 - optionator@0.9.3 - prelude-ls@1.2.1 - type-check@0.4.0 Please refer to the respective documentation and codebase of each dependency to understand how to write unit tests for them. Make sure to cover all possible scenarios and edge cases. Once the unit tests are added, run the test suite to ensure everything is working as expected. This issue was created to address the following rule: All new business logic should have corresponding unit tests.
Generating plan by analyzing files... (step 2/3)
I'm currently fixing this PR to address the following:
It seems that new dependencies have been added to the package-lock.json file without corresponding unit tests. It is important to have unit tests for all new business logic to ensure code quality and prevent regressions. Please add unit tests for the following dependencies: - @aashutoshrathi/word-wrap@1.2.6 - @eslint-community/regexpp@4.10.0 - @eslint/eslintrc@2.1.4 - @eslint/eslintrc/node_modules/globals@13.24.0 - @eslint/eslintrc/node_modules/type-fest@0.20.2 - @eslint/js@8.56.0 - @humanwhocodes/config-array@0.11.13 - @humanwhocodes/object-schema@2.0.1 - @ungap/structured-clone@1.2.0 - acorn@8.11.3 - acorn-jsx@5.3.2 - ajv@6.12.6 - espree@9.6.1 - eslint-scope@7.2.2 - eslint-visitor-keys@3.4.3 - graphemer@1.4.0 - optionator@0.9.3 - prelude-ls@1.2.1 - type-check@0.4.0 Please refer to the respective documentation and codebase of each dependency to understand how to write unit tests for them. Make sure to cover all possible scenarios and edge cases. Once the unit tests are added, run the test suite to ensure everything is working as expected. This issue was created to address the following rule: All new business logic should have corresponding unit tests.
I'm currently fixing this PR to address the following:
It appears that new dependencies have been added to the package-lock.json file without corresponding unit tests. To ensure that all new business logic has corresponding unit tests, please add unit tests for the following dependencies: - @aashutoshrathi/word-wrap (version 1.2.6) - @eslint-community/regexpp (version 4.10.0) - @eslint/eslintrc (version 2.1.4) - @eslint/eslintrc/node_modules/globals (version 13.24.0) - @eslint/eslintrc/node_modules/type-fest (version 0.20.2) - @eslint/js (version 8.56.0) - @humanwhocodes/config-array (version 0.11.13) - @humanwhocodes/object-schema (version 2.0.1) - @ungap/structured-clone (version 1.2.0) - acorn (version 8.11.3) - acorn-jsx (version 5.3.2) - ajv (version 6.12.6) - eslint (version 8.56.0) - eslint-visitor-keys (version 3.4.3) - espree (version 9.6.1) - graphemer (version 1.4.0) - optionator (version 0.9.3) - prelude-ls (version 1.2.1) - type-check (version 0.4.0) Please create unit tests for these dependencies and ensure that they are included in the test suite. This issue was created to address the following rule: All new business logic should have corresponding unit tests.
Generating plan by analyzing files... (step 2/3)
Bumps eslint from 8.37.0 to 8.56.0.
Release notes
Sourced from eslint's releases.
... (truncated)
Changelog
Sourced from eslint's changelog.
... (truncated)
Commits
8e8e9f8
8.56.0085978b
Build: changelog update for 8.56.0ba6af85
chore: upgrade@eslint/js
@8
.56.0 (#17864)60a531a
chore: package.json update for@eslint/js
release0dd9704
feat: Support custom severity when reporting unused disable directives (#17212)31a7e3f
feat: fix no-restricted-properties false negatives with unknown objects (#17818)ba87a06
chore: update dependency markdownlint to ^0.32.0 (#17783)7d5e5f6
fix:TypeError: fs.exists is not a function
on read-only file system (#17846)9271d10
chore: add GitHub issue template for docs issues (#17845)70a686b
chore: Convert rule tests to FlatRuleTester (#17819)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 show