You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When loading a schema with a type containing a property using the same name as the type itself, the hsd exported from it does only contain one hsd:entry element with that name.
That leads to the index for this index being used in both, the hsd:type element and the hsd:property element:
When loading the schema again with hale studio, it assumes the type being used in itself:
The text was updated successfully, but these errors were encountered:
The problem is that the schema that the schema reader for Shapefiles creates, in this case includes two types with the same local name and namespace, so there are two competing definitions for the same type, which is invalid and can't be represented.
Version 4.2.0.SNAPSHOT
Build 202208171957
Revision e09ae31
When loading a schema with a type containing a property using the same name as the type itself, the hsd exported from it does only contain one hsd:entry element with that name.
That leads to the index for this index being used in both, the hsd:type element and the hsd:property element:
When loading the schema again with hale studio, it assumes the type being used in itself:
The text was updated successfully, but these errors were encountered: