@dxtmisha/functional 1.11.10 → 1.11.12

package/CHANGELOG.md

@@ -2,6 +2,27 @@
 
 All notable changes to this project will be documented in this file.
 
+## [1.11.12] - 2026-05-17
+
+### Added
+- **getApiErrorRef**: Added a new helper function for reactive extraction of error objects (`ApiErrorItem`) from API response data, simplifying error handling in components.
+
+### Changed / Improved
+- **API Composables Refactoring**: Refactored `useApiRequest`, `useApiRef`, and all HTTP method-specific composables (`useApiGet`, `useApiPost`, `useApiPut`, `useApiDelete`) to support the new `ErrorCenter` and `ApiErrorStorage` contracts.
+- **Documentation**: Substantially expanded bilingual (EN/RU) JSDoc documentation for all API composables. Added detailed examples for validating response contracts using `@effect/schema` (`validateResponseContract`) and managing potential request errors via `errorContract` (`ApiErrorStorageList`).
+- **Tests**: Significantly expanded test coverage with new comprehensive unit tests for `useApiGet`, `useApiPost`, `useApiPut`, and `useApiDelete`.
+
+## [1.11.11] - 2026-05-14
+
+### Added
+- **ListDataRef**: Introduced `getFocusItem()` method to retrieve the full data object of the currently focused list item, facilitating advanced keyboard navigation and interaction handling.
+- **Types**: Added `disabled` property to the `ListDataItem` interface to support standardized state management for list items.
+
+### Changed / Improved
+- **Build System**: Refactored the distribution structure to standardize type definition paths and optimize the export map for better compatibility with modern bundlers.
+- **Peer Dependencies**: Refined the `peerDependencies` configuration to ensure more robust integration with Vue and the core functional-basic package.
+- **Maintenance**: Performed internal cleanup of the package configuration and updated build scripts to align with monorepo standards.
+
 ## [1.11.9] - 2026-05-12
 
 ### Added

package/ai-description.txt

@@ -1,5 +1 @@
-This library provides a reactive framework for Vue 3 application development, focusing on structured UI component construction, complex data management, and orchestrated API interactions. Its core purpose is to standardize component architecture through abstract base classes like DesignConstructorAbstract and to provide reactive, high-level wrappers for localized formatting (GeoIntlRef), date manipulation (DatetimeRef), and state persistence (useStorageRef, useCookieRef, useBroadcastValueRef).
-
-An AI should study this library when implementing a design system requiring standardized class-based component logic or when building data-intensive interfaces that need integrated searching, filtering, and CRUD operations via useApiManagementRef. It is indispensable for scenarios involving multi-tab state synchronization, SEO management (useMeta), and reactive internationalization (useTranslateRef) where DOM synchronization must be automated.
-
-The library integrates directly with Vue 3 and vue-router, acting as a reactive middleware layer over @dxtmisha/functional-basic. It utilizes a singleton management pattern (executeUse) for global service orchestration and relies heavily on Ref and ComputedRef to maintain its internal state machine and lifecycle hooks.
+A foundational utility and abstraction framework for Vue 3 designed to bridge functional logic with reactive component architecture. It provides a standardized constructor pattern for component development, comprehensive API orchestration, and advanced internationalization capabilities. The library is indispensable for implementing structured component lifecycles using the DesignConstructorAbstract pattern to automate the generation of dynamic classes, styles, and VNodes. It should be studied when building data-heavy interfaces requiring complex API management (GET/POST/PUT/DELETE) with integrated client-side searching, list formatting, and skeleton states via useApiManagementRef. It is critical for applications requiring deep localization, providing reactive wrappers for Intl-based formatting of numbers, currencies, dates, and geographic flag management. Use cases include managing application-wide singletons via the executeUse pattern, reactive SEO meta-tag synchronization, and specialized reactive utilities for DOM events, cookies, and IntersectionObserver integration. Built specifically for Vue 3 environments, it extends the core reactivity system with specialized computed properties and handles VNode rendering within its abstraction classes. It maintains a direct dependency on @dxtmisha/functional-basic for underlying logic and integrates with vue-router for routing-aware state management.

package/ai-doc.ru.txt

@@ -32,3 +32,14 @@
    });
    ```
 5. В самом Vue-компоненте просто импортируйте и вызывайте созданный синглтон-хук: `const { list, loading, sendPost } = useUserManagement();`
+
+ВЫБОР СТРАТЕГИИ executeUse:
+1. `executeUseLocal` (ПРЕДПОЧТИТЕЛЬНО):
+   - Когда использовать: Для большинства API-запросов и сервисов.
+   - Особенности: Работает «лениво» (lazy) — инициализируется только в момент первого вызова. Экземпляр сохраняется до конца сессии. Это позволяет не перегружать старт приложения лишними запросами.
+2. `executeUseGlobal`:
+   - Когда использовать: Когда данные или сервис должны быть загружены/инициализированы СРАЗУ при старте приложения (например: критические настройки, SDK).
+   - Особенности: Создает один экземпляр на всё приложение. Все глобальные синглтоны инициализируются принудительно через `executeUseGlobalInit()`.
+3. `executeUseProvide`:
+   - Когда использовать: Для состояния, разделяемого между родителем и группой дочерних компонентов (например: табы, сложные формы с подкомпонентами).
+   - Особенности: Использует provide/inject. Первый компонент в дереве, вызвавший хук, становится «провайдером», остальные — потребителями.

package/ai-doc.txt

@@ -32,3 +32,14 @@ Strictly follow these rules for their application:
    });
    ```
 5. Within the Vue component itself, simply import and call your custom singleton composable: `const { list, loading, sendPost } = useUserManagement();`
+
+CHOOSING THE executeUse STRATEGY:
+1. `executeUseLocal` (PREFERRED):
+   - When to use: For most API requests and services.
+   - Key Features: Works "lazily" (lazy initialization) — initializes only when first called. The instance persists until the end of the session. This prevents overloading the application start with unnecessary requests.
+2. `executeUseGlobal`:
+   - When to use: When data or a service must be loaded/initialized IMMEDIATELY at application start (e.g., critical settings, SDKs).
+   - Key Features: Creates a single instance for the entire application. All global singletons are forcibly initialized via `executeUseGlobalInit()`.
+3. `executeUseProvide`:
+   - When to use: For state shared between a parent and a group of child components (e.g., tabs, complex forms with sub-components).
+   - Key Features: Uses provide/inject. The first component in the tree that calls the hook becomes the "provider", others become consumers.