Schema exports can overwrite one another when you have two schema ids with the same ending, for example:
- https://host/segment1/test
- 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.
Schema exports can overwrite one another when you have two schema ids with the same ending, for example:
This will export the file
.../content-type-schemas/test.jsonfor 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-testandsegment2-test.