Skip to content

Schema exports can overwrite one another #123

Description

@philipbushnell-valtech

Schema exports can overwrite one another when you have two schema ids with the same ending, for example:

  1. https://host/segment1/test
  2. https://host/segment2/test

This will export the file .../content-type-schemas/test.json for both schemas; the one that is exported last is the one that remains in the file system post-export:

{
  "body": "./schemas/test-schema.json",
  "schemaId": "https://host/segment2/test",
  "validationLevel": "CONTENT_TYPE"
}

This also applies to schema json (see "body" above) and content type exported files, where the segment is lost and exported files get overwritten.

My suggestion would be to include the segment in the path so the exported naming is more like segment1-test and segment2-test.

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