What's new in EzyPlatform 1.3.0?

This release introduces dynamic EventHandler providers, improves data mapping and pagination capabilities, streamlines Admin Settings, and upgrades several core platform dependencies.
  1. Added dynamic EventHandlerProvider support
    Introduced EventHandlerProvider to allow modules and plugins to provide EventHandler and EventSchemaFetcher instances dynamically, in addition to the existing singleton-based handlers and schema fetchers. This provides greater flexibility when extending the platform's event system.
  2. Enhanced EventHandlerManager
    EventHandlerManager now falls back to provider-based handlers when no direct handler is available, supports provider handlers for VoidEvent, merges event handlers from multiple sources, retrieves schema fetchers from providers when necessary, and always returns copied collections and maps so callers can safely manipulate the results without affecting the internal cache.
  3. Improved Data Mapping filtering and pagination
    Added the fromOrToDataId filter to DefaultDataMappingFilter, allowing data mappings to be queried when a data ID may appear as either fromDataId or toDataId. Database indexes for ezy_data_mappings have also been optimized to improve pagination and filtering performance for mapping_name, from_data_id, to_data_id, numeric/text values, and mapped_at.
  4. Simplified Admin Settings
    Removed the ezyplatformNodeName setting from the Regular Settings page and its corresponding save API. The related SETTING_NODE_NAME, SettingService.getNodeName(), and AdminSettingService.setNodeName() APIs have also been removed. In addition, unused APIs such as AdminSettingService.getAllSettings() have been cleaned up to simplify the settings infrastructure.
  5. Upgraded platform dependencies
    Updated several core dependencies, including ezyhttp from 1.5.6 to 1.5.7, ezyserver from 1.3.1.3 to 1.3.1.4, and game.box from 1.2.9 to 1.3.0.