@dxtmisha/functional 1.14.1 → 1.14.4

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -2,6 +2,29 @@
2
2
 
3
3
  All notable changes to this project will be documented in this file.
4
4
 
5
+ ## [1.14.4] - 2026-06-29
6
+
7
+ ### Changed
8
+ - **GeoFlagRef**: Refactored constructor to default to `GeoRef.getLocation().value` dynamically and reactively, avoiding hard dependencies on the static `Geo.getLocation()` during SSR.
9
+ - **GeoIntlRef**: Updated fallback locale resolution to use `GeoRef.getLocation().value` instead of `GeoRef.getLanguage().value` when location is empty.
10
+
11
+ ## [1.14.3] - 2026-06-27
12
+
13
+ ### Added
14
+ - **dxtFunctionalPlugin**: Added `errorCallbacks` configuration option (type `ErrorCenterHandlerCallback[]`) to allow registering global error callbacks via `ErrorCenter.addCallback` during Vue plugin initialization.
15
+ - **dxtFunctionalPlugin**: Added unit tests verifying correct registration of global callbacks during plugin installation.
16
+
17
+ ## [1.14.2] - 2026-06-25
18
+
19
+ ### Added
20
+ - **dxtFunctionalPlugin**: Added `iconsSocial` configuration option (type `InputSocialIcons`) to allow registering custom social network icons globally via `MediaSocial.addIcons` during Vue plugin initialization.
21
+
22
+ ## [1.14.1] - 2026-06-23
23
+
24
+ ### Added
25
+ - **GeoFlagRef**: Added a new reactive wrapper class for `GeoFlag` from `@dxtmisha/functional-basic`, providing methods like `get()`, `getFlag()`, `getList()`, and `getNational()` to retrieve flags and names reactively.
26
+ - **GeoFlagRef**: Added `GeoFlagRef.test.ts` for unit testing the reactive flag behaviors.
27
+
5
28
  ## [1.14.0] - 2026-06-22
6
29
 
7
30
  ### Added
package/ai-description.md CHANGED
@@ -1,16 +1,18 @@
1
- Core Purpose: Provides a structured, reactive framework for Vue 3 component design and API orchestration. It simplifies complex UI state management, internationalization, and asynchronous API interactions through specialized classes and composables.
1
+ Core Purpose: A reactive framework for Vue 3 providing architectural abstractions for components, advanced API request orchestration with SSR support, internationalization (Intl), data list management, and global utility state synchronization.
2
2
 
3
3
  Key Expositions:
4
- - Design Construction: DesignAbstract, DesignAsyncAbstract, and DesignComponents for building complex component structures with lifecycle hooks and automated change tracking.
5
- - API Orchestration: useApiRef, useApiManagementRef (and Async variants) for handling GET/POST/PUT/DELETE requests with built-in SSR support, validation (contract-based), reactivity, and skeleton states.
6
- - Reactive Utilities: ListDataRef (list management/selection/navigation), DatetimeRef (reactive date manipulation), and GeoRef/GeoIntlRef (geo-data and internationalization).
7
- - Global State: executeUse (Global/Provide/Local patterns) for managing singletons, useMeta (global SEO management), and various storage/browser-tab sync hooks (useCookieRef, useSessionRef, useBroadcastValueRef).
8
- - Render Utilities: Helper functions for VNode rendering, class/style binding (getBind, toBind), and reactive property unwrapping (getRef, executeFunctionRef).
4
+ - Component Architecture: `DesignConstructorAbstract`, `DesignComponents`, and `DesignAbstract` provide base classes for creating reactive functional components with automatic class/style/slot handling.
5
+ - API Management: `useApiRef` (core), `useApiAsyncRef` (SSR-enabled), and `useApiManagementRef` (CRUD/list orchestration) manage requests, caching, validation (integration with `@effect/schema`), and automatic loading states.
6
+ - Reactive Utilities: `DatetimeRef`, `GeoRef`, `GeoIntlRef`, `GeoFlagRef` for locale-aware data management; `ListDataRef` for complex list manipulation; `useMeta` for reactive document head management.
7
+ - Singleton/State Factories: `executeUse` (global, provide, or local scopes) for managing shared state instances.
8
+ - Primitive Wrappers: `useCookieRef`, `useStorageRef`, `useSessionRef`, `useQueryRef`, and `useHashRef` for reactive access to browser storage and URL state.
9
9
 
10
- Triggers for Studying ai-types.md:
11
- - When encountering errors or ambiguity regarding Type constraints for API request/response contracts (`ApiDataValidation`, `ApiErrorStorageList`).
12
- - When defining complex component Props or custom UI structures that require specific type inference for classes, styles, or slots.
13
- - When implementing data lists (`ListDataRef`) or search logic that depends on strict structural compliance defined by `ListTypes` or `SearchTypes`.
14
- - When integrating the `dxtFunctionalPlugin` or configuring custom API/Translate instances.
10
+ Triggers for Studying ai-types.md:
11
+ - When implementing complex component logic involving lifecycle-dependent design systems or custom Vue components using `DesignConstructorAbstract`.
12
+ - When dealing with API state, validation contracts, or SSR pre-fetching logic (mandatory for `useApiAsyncRef` or `useApiManagementRef`).
13
+ - When defining shared singleton services or managing complex reactive states that require specific injection or scope strategies (`executeUse`).
15
14
 
16
- Integration Context: Built on top of Vue 3 and its reactivity system (Refs, Computed, EffectScope). It acts as a bridge between the `@dxtmisha/functional-basic` library and Vue, specifically handling the transformation of raw functional logic into Vue-compatible reactive objects, composables, and lifecycle-aware services.
15
+ Integration Context:
16
+ - Stack: Built for Vue 3 (Composition API).
17
+ - Dependencies: Extends `vue`, `vue-router`, and relies heavily on `@dxtmisha/functional-basic` for underlying logic.
18
+ - Infrastructure: Designed to be initialized via `dxtFunctionalPlugin` for global services (API, Translate, Meta, Router). Requires environment-aware implementation for SSR/hydration sequences.