Implement Data Fetching and Persistence in IndexDB for @dotcms/experiments Library

[oidacra]

Parent Issue

#27539

User Story

As a front-end developer, I want to implement functionality within the @dotcms/experiments library that fetches user inclusion data from the /api/v1/experiments/isUserIncluded endpoint and persists it in the browser's IndexDB, to optimize performance and enhance user experience.

Acceptance Criteria

• Data from /api/v1/experiments/isUserIncluded should be fetched efficiently upon initial user interaction with the application.
• Fetched data must be accurately persisted in the browser's IndexDB for future reference.
• Ensure that the persistence mechanism handles updates and invalidation appropriately when user data changes or when a new experiment begins.
• The implementation should include error handling for failed data fetches or IndexDB write operations.
• The solution should be encapsulated within the @dotcms/experiments library with minimal impact on the library's existing interface or functionality.

Proposed Objective

User Experience

Proposed Priority

Priority 2 - Important

dotCMS Version

master

External Links

• IndexDB API documentation: [documentation]
• @dotcms/experiments package repository

Assumptions & Initiation Needs

Quality Assurance Notes & Workarounds