What's new in EzyPlatform 1.2.0?
This release introduces a shared data-schema model in the common SDK, expands event-schema capabilities, and improves event-schema management APIs.
- Introduced CommonDataSchema in the common SDKAdded
CommonDataSchemato standardize how shared data schemas are described across the platform. This provides a reusable foundation for defining schema metadata and reduces duplication between different schema implementations. - EventSchema.DataSchema now extends CommonDataSchema
EventSchema.DataSchemanow inherits fromCommonDataSchema, consolidating commonly used schema properties such asdataType,itemType,keyType,valueType,name,required,description,example, andfieldsinto a shared model. This creates a more consistent schema definition structure across the SDK. - Added arrayItemType support for data schemasData schemas now support the
arrayItemTypeproperty, making it easier to describe the element type contained within array-based data structures. This improves schema clarity for integrations, documentation, and tooling. - Enhanced EventSchema builder architectureThe existing
EventSchema.DataSchema.builder()method remains fully supported for backward compatibility. Internally, the builder implementation now reusesCommonDataSchema.Builder, reducing duplicated code and providing a foundation for future shared schema types. The default value forrequiredis nowtrue. Optional fields should explicitly declarerequired(false). - Added EventSchemaFetcher discovery API
EventHandlerManagernow providesgetEventSchemaFetchers(), allowing applications to retrieve all registeredEventSchemaFetcherinstances. The method returns a copy of the internal list, enabling callers to inspect or manipulate the returned collection without affecting the internal state of the manager. - Priority-based EventSchemaFetcher resolution remains unchangedWhen multiple
EventSchemaFetcherinstances are registered for the sameeventName, the fetcher with the highest priority continues to take precedence. This behavior remains unchanged and ensures deterministic schema resolution.