When a table has several FK all constraints to a first table are skipped

[s13o]

When we have DDL like this

CREATE TABLE PATIENT (
  MASTER_PATIENT_IDENTIFIER STRING(MAX) NOT NULL,
  DATE_OF_BIRTH TIMESTAMP,
  FIRST_NAME STRING(MAX),
  LAST_NAME STRING(MAX),
  MIDDLE_NAME STRING(MAX),
  GENDER STRING(MAX),
) PRIMARY KEY(MASTER_PATIENT_IDENTIFIER);

CREATE TABLE FACILITY (
  FACILITY_NUMBER STRING(MAX) NOT NULL,
  FACILITY_NAME STRING(MAX),
  PRIMARY_PHONE STRING(MAX),
) PRIMARY KEY(FACILITY_NUMBER);

CREATE TABLE CARE_ACTIVITY (
  PATIENT_CARE_ACTIVITY_ID STRING(MAX) NOT NULL,
  MASTER_PATIENT_IDENTIFIER STRING(MAX) NOT NULL,
  FACILITY_NUMBER_CREATED_AT STRING(MAX),
  FACILITY_NUMBER_COMPLETED_AT STRING(MAX),
  CONSTRAINT FK_1 FOREIGN KEY(MASTER_PATIENT_IDENTIFIER) REFERENCES PATIENT(MASTER_PATIENT_IDENTIFIER),
  CONSTRAINT FK_2 FOREIGN KEY(FACILITY_NUMBER_CREATED_AT) REFERENCES FACILITY(FACILITY_NUMBER),
) PRIMARY KEY(MASTER_PATIENT_IDENTIFIER, PATIENT_CARE_ACTIVITY_ID);

the constraint FK_1 will be skipped.
If you will switch positions of the TABLE PATIENT and TABLE FACILITY in this DDL the FK_2 will be skipped.

[nktks]

spanner-er make node and subgraph for defining group internaly.
If group not exists, graph will be horizontaly long when 1:n(many) interleave relation exists.
And graphviz does not draw edge between another subgraph...

So I'll implement FK as attribute at table node, not as edge.

[s13o]

So, do you believe we should have only one FK-arrow on a diagram from the example above? Because I was unable to generate a diagram with both arrows rendered at the same time.
I just don't really sure I understood your explanation well, sorry.

[nktks]

So, do you believe we should have only one FK-arrow on a diagram from the example above?

Offcource not.
It's kind of bug of spanner-er.
But I can't fix it quickly, I just wrote the reason why I can't fix quickly.

Sorry for my bad English...