Match contains does exact matching 0.9.6.RC3+ for nested json and nested list ordering as opposed to 0.9.5

The following are passing on 0.9.5:

Feature: match_contains

    Scenario: Deeply nested contains used to work in 0.9.5 but in 0.9.6 seems to require all fields to be present
      Given def message =
      """
          {
              "correlationId": "101",
              "text": "Hello to everyone",
              "data": {
                  "deeply": {
                      "nested": "no",
                      "id": "1010"
                  }
              }
          }
          """
      Then match message contains { text: "Hello to everyone" }
      Then match message contains { data: { deeply: { nested: "no" } } } }



  Scenario: Match contains for sublist works even if simple list elements are reversed
    Given def message =
      """
      {
          order_id: 5,
          products: [100,101]
      }
      """
    Then match message contains { order_id: 5, products: [101, 100] }


  Scenario: Match contains for sublist works even if complex list elements are reversed
    Given def message =
      """
      {
          order_id: 5,
          products: [
            { product_id: 100, name: "bicycle" },
            { product_id: 101, name: "car" }
          ]
      }
      """
    Then match message contains
      """
      {
          order_id: 5,
          products: [
            { product_id: 101, name: "car" },
            { product_id: 100, name: "bicycle" }
          ]
      }
      """

0.9.6.RC3 + Latest develop (as of an hour ago or so)

Scenario 1:

match_contains.feature:22 - path: $.data.deeply, actual: {nested=no, id=1010}, expected: {nested=no}, reason: actual value has 1 more key(s) than expected: {id=1010}

Scenario 2:

21:15:30.173 [ForkJoinPool-1-worker-3] ERROR com.intuit.karate - assertion failed: path: $.products[0], actual: 100, expected: 101, reason: [path: $.products[0], actual: 100, expected: 101, reason: not equal (Integer)]

match_contains.feature:29 - path: $.products[0], actual: 100, expected: 101, reason: [path: $.products[0], actual: 100, expected: 101, reason: not equal (Integer)]

Scenario 3 equivalent of 2.

I have reproduced this here: https://github.com/KostasKgr/karate-issues/blob/match_contains_issues/src/test/java/examples/match_contains.feature

The above is with 0.9.5, tried with 0.9.6.RC3 and 2.0.0 which i hopefully built correctly from latest develop.

[ptrthomas]

@KostasKgr the rhs comes into the picture for the “docstring” variation. it will be null as a capturing group but will be set from karate internals (the stuff between the triple-quotes), I think I’ll leave as it is now

[KostasKgr]

All three scenarios I had posted pass with latest develop, cheers