-
Notifications
You must be signed in to change notification settings - Fork 32
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
fix(mockapi): dotnet compatibility failure #769
Conversation
🦋 Changeset detectedLatest commit: 35058b8 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
packages/cadl-ranch-specs/http/authentication/api-key/mockapi.ts
Outdated
Show resolved
Hide resolved
packages/cadl-ranch-specs/http/authentication/http/custom/mockapi.ts
Outdated
Show resolved
Hide resolved
dotnet uses different but compatible datetime format, so the comparison should use `coercedBodyEquals`
0c99320
to
d4edbea
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
After merge, you need to sync it back to microsoft/typespec
this is a backport of Azure/cadl-ranch#769 dotnet SDK uses a different but compatible datetime format, so we should use `coercedBodyEquals`, instead of exact match.
This is a backport of Azure/cadl-ranch#769 dotnet SDK uses a different but compatible datetime format, so we should use `coercedBodyEquals`, instead of exact match.
dotnet uses different but compatible datetime format, so the comparison should use
coercedBodyEquals
Cadl Ranch Contribution Checklist:
@scenario
names. Someone can look at the list of scenarios and understand what I'm covering.@scenarioDoc
s for extra scenario description and to tell people how to pass my mock api check.