@umituz/react-native-subscription 2.37.38 → 2.37.40

package/src/domains/paywall/README.md

@@ -1,101 +0,0 @@
-# Paywall Domain
-
-Subscription and credit purchase flow with user-friendly payment wall components and hooks.
-
-## Location
-
-- **Base Path**: `/Users/umituz/Desktop/github/umituz/apps/artificial_intelligence/npm-packages/react-native-subscription/src/domains/paywall/`
-- **Entities**: `src/domains/paywall/entities/`
-- **Components**: `src/domains/paywall/components/`
-- **Hooks**: `src/domains/paywall/hooks/`
-
-## Strategy
-
-### Paywall Management
-
-Centralized paywall system for subscription and credit purchase flows.
-
-- **Modal and Full-Screen Support**: Flexible paywall display options
-- **Multi-language Support**: Built-in i18n capabilities
-- **A/B Test Ready**: Easy creation of different paywall variants
-- **Analytics Integration**: User behavior tracking capabilities
-
-### Component Architecture
-
-Ready-to-use paywall components with customization support.
-
-- **PaywallModal**: Modal-based paywall display
-- **PaywallContainer**: Paywall content wrapper
-- **PaywallScreen**: Full-screen paywall implementation
-- **Feature Lists**: Customizable feature display components
-
-### Hook Integration
-
-Hooks for paywall state and behavior management.
-
-- **usePaywall**: Paywall visibility and state control
-- **usePaywallActions**: Purchase and restore action handling
-- **usePaywallTranslations**: Translation management
-- **useSubscriptionModal**: Subscription modal management
-
-### Configuration Strategy
-
-Theme and content customization system.
-
-- **Theme Configuration**: Custom color schemes and styling
-- **Feature Lists**: Customizable feature display
-- **Translation Support**: Multi-language copy management
-- **Event Tracking**: Analytics integration points
-
-## Restrictions
-
-### REQUIRED
-
-- **Paywall Context**: All paywall components must be used within SubscriptionProvider
-- **Config Validation**: Paywall configuration must be validated before use
-- **Error Handling**: All paywall actions must have error handling
-- **Loading States**: Purchase operations must show loading indicators
-
-### PROHIBITED
-
-- **Hardcoded Strings**: All text must support translations
-- **Direct RevenueCat Calls**: Use paywall hooks instead of direct SDK calls
-- **Missing Analytics**: All paywall interactions must be tracked
-- **Blocking UI**: Never block app flow without escape options
-
-### CRITICAL
-
-- **User Experience**: Paywalls must be dismissible
-- **Purchase Flow**: Complete purchase flow must be handled
-- **Error Recovery**: Graceful error handling required
-- **State Management**: Paywall state must be properly managed
-
-## AI Agent Guidelines
-
-### When Modifying Paywall Components
-
-1. **Maintain UX Standards**: Keep user experience consistent
-2. **Test All States**: Test loading, success, and error states
-3. **Analytics Integration**: Add tracking for new interactions
-4. **Translation Support**: All new text must be translatable
-
-### When Adding New Paywall Features
-
-1. **Hook Pattern**: Create corresponding hook for new features
-2. **Type Safety**: Define proper TypeScript types
-3. **Documentation**: Document all props and usage
-4. **Testing**: Test with different subscription states
-
-### When Fixing Paywall Bugs
-
-1. **RevenueCat Integration**: Check RevenueCat SDK integration
-2. **State Management**: Verify state transitions
-3. **Edge Cases**: Test with null/undefined states
-4. **User Flows**: Test complete purchase flows
-
-## Related Documentation
-
-- [RevenueCat Integration](/Users/umituz/Desktop/github/umituz/apps/artificial_intelligence/npm-packages/react-native-subscription/src/revenuecat/README.md)
-- [Config Domain](/Users/umituz/Desktop/github/umituz/apps/artificial_intelligence/npm-packages/react-native-subscription/src/domains/config/README.md)
-- [Wallet Domain](/Users/umituz/Desktop/github/umituz/apps/artificial_intelligence/npm-packages/react-native-subscription/src/domains/wallet/README.md)
-- [Presentation Components](/Users/umituz/Desktop/github/umituz/apps/artificial_intelligence/npm-packages/react-native-subscription/src/presentation/components/README.md)

package/src/domains/paywall/entities/README.md

@@ -1,40 +0,0 @@
-# Paywall Entities
-
-## Location
-Domain entities for paywall configuration and state management.
-
-## Strategy
-This directory contains entities representing paywall configuration, triggers, and display logic with rich context for analytics.
-
-## Restrictions
-
-### REQUIRED
-- Must include context in triggers for analytics
-- Must validate configurations before use
-- Must treat entities as immutable values
-- Must use strict TypeScript types
-
-### PROHIBITED
-- DO NOT create triggers without context
-- DO NOT use unvalidated configurations
-- DO NOT mutate entities after creation
-- DO NOT bypass type safety
-
-### CRITICAL SAFETY
-- All triggers MUST include analytics context
-- All configurations MUST be validated before use
-- All entities MUST be immutable
-- Type safety MUST be maintained
-
-## AI Agent Guidelines
-1. Include rich context in triggers for analytics tracking
-2. Validate all configurations before using them
-3. Treat all entities as immutable values
-4. Use strict TypeScript types for all properties
-5. Track all paywall events and triggers
-6. Provide clear validation error messages
-7. Test entity creation and validation thoroughly
-
-## Related Documentation
-- [Paywall README](../README.md)
-- [PaywallVisibility Hook](../../presentation/hooks/usePaywallVisibility.md)

package/src/domains/paywall/hooks/README.md

@@ -1,41 +0,0 @@
-# Paywall Hooks
-
-## Location
-React hooks for paywall management and subscription upgrades.
-
-## Strategy
-This directory contains React hooks specifically for paywall functionality with centralized state management and proper analytics tracking.
-
-## Restrictions
-
-### REQUIRED
-- Must use centralized paywall visibility state
-- Must handle authentication before purchase
-- Must store pending actions for post-purchase
-- Must track all paywall interactions
-
-### PROHIBITED
-- DO NOT use local paywall state
-- DO NOT skip authentication checks
-- DO NOT lose pending actions
-- DO NOT skip analytics tracking
-
-### CRITICAL SAFETY
-- Authentication MUST be checked before purchase
-- Pending actions MUST be preserved through purchase flow
-- All interactions MUST be tracked for analytics
-- Purchase failures MUST be handled gracefully
-
-## AI Agent Guidelines
-1. Use global state for paywall visibility management
-2. Handle authentication before initiating purchase
-3. Store pending actions for execution after purchase
-4. Track all paywall interactions for analytics
-5. Handle purchase failures with graceful recovery
-6. Show relevant paywall based on user context
-7. Test all paywall state transitions thoroughly
-
-## Related Documentation
-- [usePaywallVisibility](../../presentation/hooks/usePaywallVisibility.md)
-- [usePaywallOperations](../../presentation/hooks/usePaywallOperations.md)
-- [PremiumGate Hook](../../presentation/hooks/usePremiumGate.md)

package/src/domains/subscription/application/syncConstants.ts

@@ -1 +0,0 @@
-export const NO_SUBSCRIPTION_PRODUCT_ID = 'no_subscription';

package/src/domains/subscription/infrastructure/README.md

@@ -1,41 +0,0 @@
-# RevenueCat Infrastructure
-
-## Location
-Infrastructure layer for RevenueCat integration.
-
-## Strategy
-This directory contains concrete implementations of RevenueCat interfaces, handling communication with the RevenueCat SDK and external services with proper error handling and data transformation.
-
-## Restrictions
-
-### REQUIRED
-- Must integrate directly with RevenueCat SDK
-- Must convert SDK errors to domain errors
-- Must map SDK types to domain types
-- Must manage purchase and customer info events
-
-### PROHIBITED
-- DO NOT expose SDK errors directly to application
-- DO NOT use SDK types in domain layer
-- DO NOT skip error mapping
-- DO NOT ignore lifecycle events
-
-### CRITICAL SAFETY
-- All SDK errors MUST be converted to domain errors
-- All SDK types MUST be mapped to domain types
-- All events MUST be handled appropriately
-- Configuration MUST be set up correctly
-
-## AI Agent Guidelines
-1. Integrate directly with RevenueCat SDK
-2. Convert all SDK errors to domain errors
-3. Map all SDK types to domain types
-4. Manage purchase and customer info events properly
-5. Set up and configure RevenueCat correctly
-6. Test SDK integration thoroughly
-7. Handle all edge cases in SDK communication
-
-## Related Documentation
-- [RevenueCat Integration](../README.md)
-- [RevenueCat Application](../application/README.md)
-- [RevenueCat Domain](../domain/README.md)

package/src/domains/subscription/infrastructure/config/README.md

@@ -1,49 +0,0 @@
-# RevenueCat Infrastructure Config
-
-RevenueCat SDK configuration and initialization.
-
-## Location
-
-`src/revenuecat/infrastructure/config/`
-
-## Strategy
-
-Configuration utilities and setup for the RevenueCat SDK, providing centralized configuration management for the subscription system.
-
-## Restrictions
-
-### REQUIRED
-
-- MUST configure RevenueCat at app startup
-- MUST use valid API keys from environment configuration
-- MUST initialize before any purchase operations
-- MUST handle configuration errors gracefully
-
-### PROHIBITED
-
-- MUST NOT expose API keys in source code
-- MUST NOT hardcode configuration values
-- MUST NOT initialize RevenueCat multiple times
-- MUST NOT bypass configuration validation
-
-### CRITICAL
-
-- Always validate configuration before initialization
-- Never expose sensitive API keys or tokens
-- Handle all configuration errors gracefully
-- Ensure configuration is loaded before any operations
-
-## AI Agent Guidelines
-
-When working with RevenueCat configuration:
-1. Always validate configuration before use
-2. Never hardcode API keys or secrets
-3. Handle all configuration errors gracefully
-4. Ensure proper initialization order
-5. Test with both valid and invalid configurations
-
-## Related Documentation
-
-- [Managers](../managers/README.md)
-- [Services](../services/README.md)
-- [RevenueCat README](../../README.md)

package/src/domains/subscription/infrastructure/handlers/README.md

@@ -1,41 +0,0 @@
-# RevenueCat Infrastructure Handlers
-
-## Location
-Event handlers for RevenueCat lifecycle events.
-
-## Strategy
-This directory contains handler implementations for managing RevenueCat events including purchase callbacks, customer info changes, and error handling with proper data validation and recovery.
-
-## Restrictions
-
-### REQUIRED
-- Must handle all events gracefully
-- Must validate incoming data before processing
-- Must log all events for debugging
-- Must invoke callbacks appropriately
-
-### PROHIBITED
-- DO NOT mutate incoming event data
-- DO NOT ignore event handling errors
-- DO NOT skip callback invocation
-- DO NOT process unvalidated data
-
-### CRITICAL SAFETY
-- All incoming data MUST be validated
-- All events MUST be logged for debugging
-- All callbacks MUST be invoked appropriately
-- Recovery options MUST be provided when possible
-
-## AI Agent Guidelines
-1. Never mutate incoming event data
-2. Handle all errors gracefully with proper boundaries
-3. Log all events for debugging and monitoring
-4. Invoke registered callbacks appropriately
-5. Use async/await for asynchronous operations
-6. Validate all incoming data before processing
-7. Provide recovery options when possible
-
-## Related Documentation
-- [RevenueCat Infrastructure](../README.md)
-- [RevenueCat Services](../services/README.md)
-- [RevenueCat Errors](../../domain/errors/README.md)

package/src/domains/subscription/infrastructure/hooks/README.md

@@ -1,50 +0,0 @@
-# RevenueCat Presentation Hooks
-
-React hooks for accessing RevenueCat data and operations.
-
-## Location
-
-`src/revenuecat/presentation/hooks/`
-
-## Strategy
-
-React hooks that expose RevenueCat functionality to the presentation layer, providing access to customer info, subscription packages, and offerings.
-
-## Restrictions
-
-### REQUIRED
-
-- MUST handle loading states appropriately
-- MUST handle error states gracefully
-- MUST cache responses when appropriate
-- MUST subscribe to real-time updates when needed
-- MUST validate all data before use
-
-### PROHIBITED
-
-- MUST NOT expose RevenueCat implementation details to components
-- MUST NOT bypass error handling
-- MUST NOT create infinite loops with subscriptions
-- MUST NOT assume data is always available
-
-### CRITICAL
-
-- Always handle loading and error states
-- Unsubscribe from all listeners on unmount
-- Validate all data before using it in components
-- Handle null/undefined states properly
-
-## AI Agent Guidelines
-
-When working with RevenueCat hooks:
-1. Always handle loading and error states
-2. Unsubscribe from listeners on unmount
-3. Validate all data before use
-4. Cache responses appropriately
-5. Handle null/undefined states gracefully
-
-## Related Documentation
-
-- [Main Hooks](../../../presentation/hooks/README.md)
-- [Domain](../../domain/README.md)
-- [Services](../infrastructure/services/README.md)

package/src/domains/subscription/infrastructure/managers/README.md

@@ -1,41 +0,0 @@
-# RevenueCat Infrastructure Managers
-
-## Location
-Manager classes for coordinating RevenueCat operations.
-
-## Strategy
-This directory contains high-level manager classes that coordinate between different RevenueCat services and handle complex operations like SDK configuration and entitlement access.
-
-## Restrictions
-
-### REQUIRED
-- Must coordinate between services properly
-- Must manage SDK configuration correctly
-- Must provide access to entitlement IDs
-- Must handle complex operations safely
-
-### PROHIBITED
-- DO NOT bypass service coordination
-- DO NOT misconfigure SDK
-- DO NOT expose invalid entitlement IDs
-- DO NOT oversimplify complex operations
-
-### CRITICAL SAFETY
-- Service coordination MUST be correct
-- SDK configuration MUST be valid
-- Entitlement access MUST be safe
-- Complex operations MUST be handled properly
-
-## AI Agent Guidelines
-1. Coordinate properly between RevenueCat services
-2. Manage SDK configuration with correct parameters
-3. Provide safe access to entitlement IDs
-4. Handle complex operations with proper error handling
-5. Test coordination logic thoroughly
-6. Document manager responsibilities clearly
-7. Maintain separation of concerns
-
-## Related Documentation
-- [Services](../services/README.md)
-- [Config](../config/README.md)
-- [Domain](../../domain/README.md)

package/src/domains/subscription/infrastructure/services/README.md

@@ -1,42 +0,0 @@
-# RevenueCat Infrastructure Services
-
-## Location
-Service implementations for RevenueCat operations.
-
-## Strategy
-This directory contains concrete implementations of RevenueCat interfaces, providing the actual integration with the RevenueCat SDK using singleton pattern with proper error handling and caching.
-
-## Restrictions
-
-### REQUIRED
-- Must use singleton pattern for service instance
-- Must wrap all service calls in try-catch
-- Must use TypeScript types for all operations
-- Must log all RevenueCat operations
-
-### PROHIBITED
-- DO NOT create multiple service instances
-- DO NOT skip error handling
-- DO NOT bypass type safety
-- DO NOT skip logging operations
-
-### CRITICAL SAFETY
-- Service MUST be configured only once
-- All calls MUST be wrapped in error handling
-- All operations MUST be type-safe
-- All operations MUST be logged
-
-## AI Agent Guidelines
-1. Use singleton pattern for service instance
-2. Wrap all service calls in try-catch blocks
-3. Use TypeScript types for all operations
-4. Log all RevenueCat operations for debugging
-5. Cache customer info and offerings appropriately
-6. Validate parameters before calling SDK
-7. Configure service only once at startup
-8. Use mock implementations for testing
-
-## Related Documentation
-- [RevenueCat Infrastructure](../README.md)
-- [RevenueCat Handlers](../handlers/README.md)
-- [RevenueCat Application Ports](../../application/ports/README.md)

package/src/domains/subscription/infrastructure/utils/README.md

@@ -1,41 +0,0 @@
-# RevenueCat Infrastructure Utils
-
-## Location
-Utility functions for RevenueCat operations.
-
-## Strategy
-This directory contains utility functions for common RevenueCat operations including error mapping, data transformation, validation, and formatting with proper type safety.
-
-## Restrictions
-
-### REQUIRED
-- Must use error mapping for user-facing messages
-- Must ensure types are validated before use
-- Must respect user locale for formatting
-- Must check for null/undefined values
-
-### PROHIBITED
-- DO NOT show SDK errors directly to users
-- DO NOT use data without type validation
-- DO NOT ignore locale settings
-- DO NOT skip null checks
-
-### CRITICAL SAFETY
-- All errors MUST be mapped to domain errors
-- All types MUST be validated before use
-- Locale MUST be respected for formatting
-- Null checks MUST be performed consistently
-
-## AI Agent Guidelines
-1. Always map SDK errors to domain errors for user-facing messages
-2. Ensure type safety by validating types before use
-3. Respect user locale when formatting prices and periods
-4. Always check for null/undefined values before processing
-5. Use debug helpers in development for troubleshooting
-6. Validate all data before processing
-7. Test utility functions with edge cases
-
-## Related Documentation
-- [RevenueCat Infrastructure](../README.md)
-- [RevenueCat Domain Types](../../domain/types/README.md)
-- [RevenueCat Errors](../../domain/errors/README.md)

package/src/domains/subscription/presentation/components/README.md

@@ -1,155 +0,0 @@
-# Presentation Components
-
-React Native UI components for subscription and paywall features.
-
-## Location
-
-**Directory**: `src/presentation/components/`
-
-**Type**: Component Library
-
-## Strategy
-
-### Component Categories
-
-Components are organized by functionality:
-
-1. **Details Components**
-   - CreditRow: Display credit balance and info
-   - DetailRow: Generic detail display row
-   - PremiumStatusBadge: Visual premium indicator
-   - PremiumDetailsCard: Premium subscription details
-
-2. **Feedback Components**
-   - PaywallFeedbackModal: User feedback collection
-   - Alert components: Warning and info displays
-
-3. **Section Components**
-   - SubscriptionSection: Subscription info section
-   - CreditsSection: Credits balance section
-
-4. **Paywall Components**
-   - PaywallModal: Upgrade/purchase modal
-   - Purchase options: Subscription and credit packages
-
-### Design Principles
-
-All components follow these principles:
-- **Reusable**: Composable and configurable
-- **Typed**: Full TypeScript support
-- **Accessible**: WCAG compliant where possible
-- **Testable**: Easy to test in isolation
-- **Themeable**: Support custom styling
-
-### Integration Points
-
-- **React Native**: Core UI framework
-- **Design System**: Shared UI components
-- **Localization**: i18n string support
-- **Theme**: Custom styling support
-
-## Restrictions
-
-### REQUIRED
-
-- **Props Typing**: All components MUST have TypeScript interfaces
-- **Default Props**: MUST provide sensible defaults
-- **Accessibility**: MUST implement accessibility labels
-- **Responsive**: MUST handle different screen sizes
-
-### PROHIBITED
-
-- **NEVER** hardcode colors or sizes (use theme)
-- **NEVER** include business logic in components
-- **DO NOT** make direct API calls
-- **NEVER** hardcode strings (use localization)
-
-### CRITICAL SAFETY
-
-- **ALWAYS** validate props before rendering
-- **ALWAYS** handle loading and error states
-- **NEVER** trust user input for security decisions
-- **MUST** implement proper error boundaries
-- **ALWAYS** sanitize user-provided content
-
-## AI Agent Guidelines
-
-### When Building Components
-
-1. **Always** define TypeScript interfaces for props
-2. **Always** use theme for styling (no hardcoded values)
-3. **Always** implement accessibility labels
-4. **Always** handle loading and error states
-5. **Never** include business logic in components
-
-### Integration Checklist
-
-- [ ] Define TypeScript interface for props
-- [ ] Use theme for all styling
-- [ ] Implement accessibility labels
-- [ ] Handle loading state
-- [ ] Handle error state
-- [ ] Provide sensible defaults
-- [ ] Test with different screen sizes
-- [ ] Test accessibility
-- [ ] Test with various prop combinations
-- [ ] Document component usage
-
-### Common Patterns
-
-1. **Compound Components**: Build complex UIs from simple parts
-2. **Render Props**: Share stateful logic
-3. **Slot Pattern**: Allow content injection
-4. **Control Props**: Make components controlled or uncontrolled
-5. **Asynchronous States**: Handle loading, error, success states
-6. **Responsive Design**: Adapt to different screen sizes
-7. **Theme Integration**: Use design system tokens
-8. **Accessibility First**: Include a11y from the start
-
-## Related Documentation
-
-- **Details Components**: `details/README.md`
-- **Feedback Components**: `feedback/README.md`
-- **Section Components**: `sections/README.md`
-- **Paywall Components**: `paywall/README.md`
-- **Design System**: External design system documentation
-- **Hooks**: `../hooks/README.md`
-
-## Component Examples
-
-### CreditRow
-
-Display user's credit balance with optional actions.
-
-Usage:
-- Set amount prop to number of credits
-- Set isLoading to true during data fetch
-- Provide onPress callback for navigation
-- Component displays credit count and handles tap
-
-### PremiumStatusBadge
-
-Visual indicator for premium subscription status.
-
-Usage:
-- Set isPremium to boolean status
-- Set tier to subscription level (gold, silver, etc.)
-- Component renders styled badge
-
-### PaywallModal
-
-Modal for subscription and credit purchase.
-
-Usage:
-- Set isVisible to boolean for show/hide
-- Provide onClose callback
-- Pass features array for premium features list
-- Modal handles purchase flow
-
-## Directory Structure
-
-The components directory contains:
-- **details/** - Detail display components (CreditRow, DetailRow, PremiumStatusBadge, PremiumDetailsCard)
-- **feedback/** - Feedback and alert components (PaywallFeedbackModal)
-- **sections/** - Section components (SubscriptionSection)
-- **paywall/** - Paywall components (PaywallModal)