-
Notifications
You must be signed in to change notification settings - Fork 170
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Regression v8.3.0] Incorrect error: Adding route with same name or matcher as existing route. #493
Comments
This was referenced Jan 2, 2020
Thanks for the bug report. Fix on its way. |
fixed in 8.3.1 |
jeremymeng
added a commit
to jeremymeng/azure-sdk-for-js
that referenced
this issue
Jan 28, 2020
Resolves Azure#6714 There was a regression in fetch-mock wheresrhys/fetch-mock#493 which is already fixed in the latest version of fetch-mock.
jeremymeng
added a commit
to Azure/azure-sdk-for-js
that referenced
this issue
Jan 28, 2020
) * [core-http][test] revert workaround of pinning fetch-mock version Resolves #6714 There was a regression in fetch-mock wheresrhys/fetch-mock#493 which is already fixed in the latest version of fetch-mock. * Update pnpm-lock.yaml
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Minimal test case
In
fetch-mock
v8.2.1, it just logsdone.
.When running the same code in v8.3.0, it throws the following error
The text was updated successfully, but these errors were encountered: