Object can be null or have value

Hi, This is a question. What is the best way for me to define something like below in Pact Fragment -

"Certification": {
    "Java": {
        "Version": "1.7",
        "Year": "2015" 
    },
    "Scala": null,
    "C#": null,
    "C": null,
}

So basically inside Certification object, each object can be null or have some additional fields.

What would be a good way to do this so it accepts values or null?

[bengro]

This is a real shame to not support conditional parts in responses. Is there no solution/workaround to this problem still?

Given I have different types of objects:

[
  {
    type: "TYPE_A"
  },
  {
    type: "TYPE_B"
  }
]

I would like to be able to write a matcher, which only focuses on TYPE_A, hence making my matching rules conditional on the type.

Given the schema-less nature of JSON, this should definitely be supported.

[uglyog]

@alonpeer has described a elegant solution if you are able to change the format of the JSON.

As to optional values, we don’t really support them (the idea is to leave optional things out and only include the important things in the contract. Also see https://docs.pact.io/faq/#why-is-there-no-support-for-specifying-optional-attributes)

There is a specification change proposed (https://github.com/pact-foundation/pact-specification/tree/version-4#additional-matchers) to introduce an or condition with additional matchers, but it is a work in progress.