chore(deps-dev): bump axios-mock-adapter from 1.22.0 to 2.0.0

[dependabot]

Bumps axios-mock-adapter from 1.22.0 to 2.0.0.

Release notes

Sourced from axios-mock-adapter's releases.

v2.0.0

Breaking Changes 💥

• Drop node versions lower than v18 (ctimmerm/axios-mock-adapter#390)

• Change the parameters of the methods to align it to the one of axios. (ctimmerm/axios-mock-adapter#387) The last parameter must be a config object with {params, headers} instead of just the headers. If you've always only used two parameters, you won't have to change anything.

  Methods with data param:

  • mock.onPost(url, data, headers) > mock.onPost(url, data, {params, headers})
  • mock.onPut(url, data, headers) > mock.onPost(url, data, {params, headers})
  • mock.onPatch(url, data, headers) > mock.onPatch(url, data, {params, headers})
  • mock.onAny(url, data, headers) > mock.onAny(url, {data, params, headers})

  Methods without data param:

  • mock.onGet(url, {params}, headers) > mock.onGet(url, {params, headers})
  • mock.onDelete(url, {params}, headers) > mock.onDelete(url, {params, headers})
  • mock.onHead(url, {params}, headers) > mock.onHead(url, {params, headers})
  • mock.onOptions(url, {params}, headers) > mock.onOptions(url, {params, headers})

  An error is reported if one accidentally passes the headers directly instead of `{headers: {}}.

  e.g. Error: Invalid config property Header-test provided to onPatch. Config: {"Header-test":"test-header"}

Commits

• 113656e 2.0.0
• 306e40f Subtract -1 on the delay tests as the setTimeout resolution behaves weird and...
• ab4bb17 Change Date.now() to performance.now()
• 999ef1c Try to fix flaky delay tests
• e68e418 Strip out undefined headers during axios header normalization to not cause as...
• 99cf5e9 Improve 'Could not find mock for' message by providing headers and params con...
• f45c074 Revert types of onLink, onUnlink and onList
• 617b0c7 Add assertions to detect wrong config options of the breaking change
• d491b04 Support axios-like config object with params, headers and data attributes
• 5635cc6 Support params comparisons for post and put requests
• 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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @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)

[changeset-bot]

⚠️ No Changeset found

Latest commit: 6ab5532

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[coderabbitai]

Warning

Rate limit exceeded

@dependabot[bot] has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 28 minutes and 47 seconds before requesting another review.

How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

Commits

Files that changed from the base of the PR and between 4f5783d and 6ab5532.

---

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?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.