@dxtmisha/functional-basic 1.3.15 → 1.4.1

package/CHANGELOG.md

@@ -2,6 +2,20 @@
 
 All notable changes to this project will be documented in this file.
 
+## [1.4.0] - 2026-06-22
+
+### Added
+- **UrlInstanceAbstract**: Created base abstract class managing shared reactive state properties and methods (`data`, `watch`, `block`, `time`, `get()`, `set()`, `addWatch()`, `removeWatch()`, `reload()`, `initData()`, `makeWatch()`) for URL-based state instances.
+- **UrlItem**: Added `getParams()` to parse URL parameters into an object with type transformations, and `setParams(params)` to replace and filter empty, null, or undefined parameters.
+- **UrlItem**: Added comprehensive unit tests in `UrlItem.test.ts` for verifying parameter retrieval and mutation logic.
+
+### Changed
+- **HashInstance**: Refactored to extend `UrlInstanceAbstract`, inheriting all core state management properties and handlers.
+- **QueryInstance**: Refactored to extend `UrlInstanceAbstract` and delegate query parameter reading/writing to `UrlItem.getParams()` and `UrlItem.setParams()`, ensuring SSR compatibility.
+
+### Fixed
+- **QueryInstance**: Updated `QueryInstance.test.ts` to run under the `jsdom` test environment, fixing `window is not defined` execution errors, and enhanced mocking setup.
+
 ## [1.3.15] - 2026-06-19
 
 ### Added

package/ai-description.md

@@ -1,18 +1,25 @@
-Core Purpose: This library provides a comprehensive, isomorphic toolkit for web applications, specifically focusing on SSR-ready API interaction, state-consistent storage (Cookies, Local/SessionStorage, ServerStorage), internationalization (i18n), and robust DOM event/UI management.
+The provided library is a comprehensive isomorphic toolkit for managing frontend and SSR-compatible application states, including API requests, internationalization, data persistence, and UI utilities.
+
+Core Purpose:
+Facilitates full-stack state management and utility-based data handling, providing standardized interfaces for HTTP requests (with caching and error handling), localization (Geo/Translation), storage (Cookie/Storage/Hash/Query), and DOM event synchronization.
 
 Key Expositions:
-- Api: Centralized HTTP client managing requests, hydration, caching (ApiCache), and centralized error handling (ApiErrorStorage).
-- Storage: Persistent utilities including DataStorage (local/session), CookieStorage, and ServerStorage (SSR-aware).
-- Geo & Locale: GeoInstance, GeoIntl, and GeoFlag provide location-aware formatting (currencies, dates, numbers, units, phone masks).
-- UI/Utility: Meta management (Meta, MetaOg, MetaTwitter), event handling (EventItem), icon management (Icons), and search utilities (SearchList).
-- Formatting: Formatters class for templated data manipulation (currency, date, pluralization, unit conversion).
+- Api: Singleton-based HTTP client (supports fetch, caching, hydration, and error normalization via ApiErrorStorage).
+- Geo & GeoIntl: Internationalization framework for locale-aware number, date, currency, and phone number formatting.
+- Meta, MetaOg, MetaTwitter: Declarative meta-tag management for SEO and social sharing.
+- DataStorage & CookieStorage: Persistent storage wrappers (LocalStorage/SessionStorage/Cookie) with SSR context isolation.
+- EventItem: Reactive DOM event wrapper supporting ResizeObserver and scroll synchronization.
+- Translate & TranslateFile: Asynchronous translation engine with support for dynamic loading and key replacement.
+- SearchList: Logic for client-side search indexing, matching, and highlighting within data lists.
+- Utils: A broad collection of pure functional utilities (e.g., `copyObject`, `toNumber`, `isFilled`, `sleep`, `frame`).
 
 Triggers for Studying ai-types.md:
-- When implementing API integration (Api, ApiFetch, ApiMethod).
-- When configuring global error handling (ErrorCenter, ApiError).
-- When managing SSR state or hydration (ServerStorage, ApiHydration).
-- When handling localization (Geo, GeoIntl, Translate, Formatters).
-- When configuring complex data search logic (SearchList, SearchColumns).
-- When defining custom meta-tags or Twitter/Open Graph cards (Meta, MetaOg, MetaTwitter).
+- When implementing or debugging API integration (Api, ApiInstance, ApiResponse).
+- When configuring global error handling (ErrorCenter).
+- When standardizing data localization or date/time formatting (Geo, GeoIntl, Datetime).
+- When managing complex SSR hydration patterns (ServerStorage, ApiHydration).
+- When integrating deep-search components (SearchList).
+- When developing custom UI components requiring lifecycle-safe event binding (EventItem).
 
-Integration Context: This library acts as a foundational service layer. It is designed to be injected or used as a singleton across the application stack, bridging client-side DOM operations with server-side context in SSR frameworks. It manages the lifecycle of data, authentication headers, and global configuration, serving as an abstraction layer over native Browser/Node.js APIs like fetch, Cookies, and BroadcastChannel.
+Integration Context:
+Operates as a foundational layer in the stack, compatible with both browser and Node.js (SSR) environments. It acts as a dependency for managing global application state, handling data-driven side effects, and normalizing communication with backend services. It is designed to be injected into frameworks (Vue/React) via lifecycle hooks or custom configuration providers.