Skip to content

Patches erroneously declare a top-level allOf with a value of null #13

Description

@mrshll1001

There are multiple cases where the Profile patches add a top-level allOf property with a value of null. These should be removed as it does not do anything, and is likely a result of misinterpreting the instructions for adding new sets of required fields.

The following schemas are affected:

  • accessibility.json
  • address.json
  • attribute.json
  • contact.json
  • cost_option.json
  • funding.json
  • language.json
  • location.json
  • openapi.json
  • organization.json
  • phone.json
  • schedule.json
  • service_area.json
  • service_at_location.json
  • service.json
  • taxonomy.json
  • taxonomy_term.json

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions