Skip to content
This repository has been archived by the owner on Jun 28, 2022. It is now read-only.

Incorrect optionality of attributes #17

Open
mjcgm opened this issue Jul 2, 2019 · 0 comments
Open

Incorrect optionality of attributes #17

mjcgm opened this issue Jul 2, 2019 · 0 comments

Comments

@mjcgm
Copy link

mjcgm commented Jul 2, 2019

The optionality of the attributes is not considered correctly. E.g. in the generated Swagger file, the Patient.gender is said to be required although the conformance statement doesn't. We used

fhir-swagger --fhir_url http://test.fhir.org/r3 --conformance_path="/metadata?_format=application/json" --dstu3 --output r3.json

and got

    ...
    "Patient": {
      "description": "",
      "type": "object",
      "properties": {
        ...
        "gender": {
          "type": "string",
          "minLength": 1
        },
        ...
      },
      "required": [
        "resourceType",
        "id",
        "text",
        "identifier",
        "active",
        "name",
        "gender",
        "photo",
        "contact",
        "managingOrganization",
        "link"
      ]
    },
    ...
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant