Documentation for match contains does not reflect changes in 0.9.6

[gavl-cdl]

The second example in the documentation for match contains states:

Note that match contains will "recurse", so any nested JSON chunks will also be matched using match contains:
* def original = { a: 1, b: 2, c: 3, d: { a: 1, b: 2 } }
* def expected = { a: 1, c: 3, d: { b: 2 } }
* match original contains expected

But this example fails in 0.9.6 (line break added for readability):

assertion failed: path: $.d, actual: {a=1, b=2}, expected: {b=2},
reason: actual value has 1 more key(s) than expected: {a=1}

Indeed, the documentation for the new match contains deep and the 0.9.6 release notes both use this same example to describe the difference between match contains and match contains deep

IMO, this should probably be mentioned in the "breaking changes" section of the release notes, because it will cause existing feature files to fail if they rely on the old recursive-contains behaviour

[ptrthomas]

thanks for raising this. fixed and release-notes updated

[gavl-cdl]

Wow, <1 hour to fixed. Thanks!