does atMost(1) matcher rule break postel's law? Be...
# general
s
does atMost(1) matcher rule break postel's law? Because let's say atMost(0) that's probably not allowed, because you're basically saying "return empty list", which is akin to say "return no list" which breaks this https://docs.pact.io/getting_started/matching/gotchas#you-cannot-expect-a-field-to-not-be-present-in-a-response but does saying atMost(1) also break the clause "you cannot test for absence of something", cause you're testing for absence of elements beyond 1?
r
I think that should be a guiding principle and not an absolute law. If using
atMost(1)
makes sense to use, then people are stating they never expect more than one value.
👍 1
s

https://media4.giphy.com/media/v1.Y2lkPTc5MGI3NjExYWxmdm4xZmw5NGVjb2NqdjdxYmM0anJ0YTc1aWtrazB3ejNieW43ZyZlcD12MV9pbnRlcm5hbF9naWZfYnlfaWQmY3Q9Zw/uXUmaREltwja1dEqXi/giphy.gif▾