-
-
Notifications
You must be signed in to change notification settings - Fork 213
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
Mapping adding order matters for multiple mappings? #344
Comments
The first doesn't have a match on body. Is that intended? |
Yes. I want to have 2 mappings where one more strict with specific body and the other more general for requests without such body |
I see. The code does just take the first available match: Maybe it a good idea to also take into account the number of successful matches. |
Oh so it does not matter the total score of the matchings? I would assume that it should return the best matching available and not the first one.. |
@gregoks |
Ill try. Does it include the other bug fixes? Because I already use the WireMock.Net.1.0.31-ci-11865 version. |
No, this one is only this fix. The #339 is not included here. |
I've tested and its working in WireMock.Net.1.0.30-ci-11883 version. Thanks!! Do you have an ETA for version that will include all of the current open bug fixes? Thanks, Greg |
No ETA, yet. Please keep a watch on this project + Nuget. |
* Fix CompareTo in RequestMatchResult #344 * fix test
hi,
I have a weird behavior for these 2 mappings that I'm adding.
I'm sending the following request:
body:
<xml>555</xml>
headers:
I'm creating 2 mappings (dont mind the mapping guids):
The thing that it seems that if I add the first mapping first then its get caught and the other way around then the 2nd mapping gets caught:
example of the admin/requests when first mapping added first:
example of the admin/requests when second mapping added first:
Can you please check if I'm missing anything?
The text was updated successfully, but these errors were encountered: