@umituz/react-native-subscription 2.37.38 → 2.37.40

package/src/domains/subscription/presentation/components/paywall/PaywallModal.md

@@ -1,94 +0,0 @@
-# PaywallModal Component
-
-Modal paywall component for subscription upgrade.
-
-## Location
-
-**Import Path**: `@umituz/react-native-subscription`
-
-**File**: `src/presentation/components/paywall/PaywallModal.tsx`
-
-**Type**: Component
-
-## Strategy
-
-### Paywall Display Flow
-
-1. **Modal Visibility**: Control visibility via isVisible prop
-2. **Configuration**: Display features, pricing, and benefits
-3. **Package Display**: Show available subscription packages
-4. **Purchase Handling**: Handle purchase initiation and completion
-5. **Close Behavior**: Handle modal close/dismissal
-6. **Responsive Design**: Adapt to different screen sizes
-
-### Integration Points
-
-- **usePaywallVisibility**: For modal visibility control
-- **useSubscriptionPackages**: For available packages
-- **usePaywallOperations**: For purchase handling
-- **Analytics**: For tracking impressions and conversions
-- **Navigation**: For post-purchase navigation
-
-## Restrictions
-
-### REQUIRED
-
-- **Visibility Control**: MUST control via isVisible prop
-- **Close Handler**: MUST provide onClose callback
-- **Purchase Handler**: MUST implement onPurchase callback
-- **Package Display**: MUST show available packages
-
-### PROHIBITED
-
-- **NEVER** trap users without close option
-- **NEVER** show without user trigger or clear reason
-- **DO NOT** show too frequently
-- **DO NOT** hide pricing information
-
-### CRITICAL SAFETY
-
-- **ALWAYS** provide clear close button
-- **NEVER** trap users in modal
-- **MUST** handle all purchase outcomes
-- **ALWAYS** show pricing clearly
-
-## AI Agent Guidelines
-
-### When Implementing Paywall Modals
-
-1. **Always** provide clear close button
-2. **Always** show pricing transparently
-3. **Always** handle all purchase outcomes
-4. **Always** track impressions and conversions
-5. **Never** trap users without exit
-
-### Integration Checklist
-
-- [ ] Import from correct path: `@umituz/react-native-subscription`
-- [ ] Control visibility via isVisible prop
-- [ ] Implement onClose callback
-- [ ] Implement onPurchase callback
-- [ ] Configure features and benefits
-- [ ] Display package options
-- [ ] Handle loading states
-- [ ] Track analytics events
-- [ ] Test purchase flow
-- [ ] Test close behavior
-- [ ] Verify responsive design
-
-### Common Patterns
-
-1. **Manual Trigger**: Show on button press
-2. **Usage Limit**: Show after N free uses
-3. **Feature Gate**: Show when accessing premium feature
-4. **Time-based**: Show after certain time/usage
-5. **Event-driven**: Show on specific app events
-6. **A/B Testing**: Test different copy and layouts
-
-## Related Documentation
-
-- **usePaywall**: Paywall state management
-- **usePaywallOperations**: Purchase operations
-- **usePaywallVisibility**: Visibility control
-- **PaywallDomain**: `../../../domains/paywall/README.md`
-- **Paywall README**: `./README.md`

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

@@ -1,54 +0,0 @@
-# Paywall Components
-
-UI components specifically designed for paywall and subscription upgrade screens.
-
-## Location
-
-`src/presentation/components/paywall/`
-
-## Strategy
-
-Specialized components for displaying paywalls, package selection, and subscription upgrade prompts. These components handle the visual presentation of subscription offers and user purchase flows.
-
-## Restrictions
-
-### REQUIRED
-
-- Must use design tokens for consistent styling
-- Must support multiple display modes (card, list, minimal)
-- Must include loading states
-- Must handle accessibility requirements
-- Must support screen readers
-- Must provide proper touch targets
-
-### PROHIBITED
-
-- MUST NOT hardcode pricing or product information
-- MUST NOT bypass payment validation
-- MUST NOT expose RevenueCat implementation details
-- MUST NOT create custom payment flows outside approved patterns
-
-### CRITICAL
-
-- All purchase flows MUST go through RevenueCat
-- Never log or transmit sensitive payment information
-- Always handle errors gracefully with user-friendly messages
-- Must support cancellation and refund flows
-
-## AI Agent Guidelines
-
-When modifying paywall components:
-1. Maintain visual hierarchy for recommended packages
-2. Ensure clear pricing display (price, period, per-month equivalent)
-3. Keep features easy to understand
-4. Include social proof elements (ratings, reviews, user counts)
-5. Add trust signals (guarantees, badges, certifications)
-6. Optimize for mobile screens
-7. Lazy load images and avoid expensive animations
-8. Always support accessibility standards
-
-## Related Documentation
-
-- [Paywall Domain](../../../domains/paywall/README.md)
-- [Paywall Hooks](../../hooks/README.md)
-- [RevenueCat Integration](../../../revenuecat/README.md)

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

@@ -1,99 +0,0 @@
-# Sections Components
-
-Subscription-related section and card components.
-
-## Location
-
-- **Base Path**: `/Users/umituz/Desktop/github/umituz/apps/artificial_intelligence/npm-packages/react-native-subscription/src/presentation/components/sections/`
-- **Components**: `src/presentation/components/sections/`
-
-## Strategy
-
-### Section Components
-
-Organized sections for subscription information display.
-
-- **SubscriptionSection**: Subscription status and management section
-- **Status Display**: Clear status indicators
-- **Action Buttons**: Management and upgrade actions
-- **Navigation Support**: Deep linking to detail screens
-
-### Display Features
-
-Comprehensive subscription information display.
-
-- **Status Indicators**: Active/inactive status display
-- **Expiration Dates**: Date formatting and display
-- **Management Actions**: Subscription management buttons
-- **Upgrade Options**: Premium upgrade prompts
-
-### Interaction Design
-
-User-friendly interaction patterns.
-
-- **Press Actions**: Navigation to detail screens
-- **Long Press**: Quick management options
-- **Status-Based UI**: Different UI for different subscription states
-- **Refresh Support**: Pull-to-refresh capabilities
-
-### Customization
-
-Flexible styling and behavior.
-
-- **Custom Actions**: Custom action handlers
-- **Style Props**: Custom styling support
-- **Translation Support**: Multi-language support
-- **Conditional Display**: Show/hide elements based on state
-
-## Restrictions
-
-### REQUIRED
-
-- **Status Clarity**: Status must be clearly visible
-- **Action Buttons**: Provide appropriate action buttons
-- **Loading States**: Show loading indicators
-- **Error Handling**: Handle errors gracefully
-
-### PROHIBITED
-
-- **Hardcoded Text**: All text must support translations
-- **Missing Actions**: Never omit necessary actions
-- **Ambiguous Status**: Status must be unambiguous
-- **Blocking UI**: Never block app navigation
-
-### CRITICAL
-
-- **Deep Links**: Include management deep links
-- **State Accuracy**: Display accurate subscription state
-- **User Actions**: Provide clear action options
-- **Platform Links**: Correct platform-specific management links
-
-## AI Agent Guidelines
-
-### When Modifying Section Components
-
-1. **Component Interface**: Maintain consistent prop interfaces
-2. **State Handling**: Proper state management
-3. **Translations**: Ensure translation support
-4. **Accessibility**: Include accessibility features
-
-### When Adding Section Features
-
-1. **Pattern Consistency**: Follow existing patterns
-2. **Type Safety**: Define TypeScript types
-3. **Documentation**: Document props and usage
-4. **Testing**: Test with different subscription states
-
-### When Fixing Section Component Bugs
-
-1. **State Display**: Check state display logic
-2. **Actions**: Verify action handlers
-3. **Navigation**: Test navigation flows
-4. **Edge Cases**: Test with null/undefined states
-
-## Related Documentation
-
-- [Details Components](/Users/umituz/Desktop/github/umituz/apps/artificial_intelligence/npm-packages/react-native-subscription/src/presentation/components/details/README.md)
-- [Feedback Components](/Users/umituz/Desktop/github/umituz/apps/artificial_intelligence/npm-packages/react-native-subscription/src/presentation/components/feedback/README.md)
-- [Presentation Components](/Users/umituz/Desktop/github/umituz/apps/artificial_intelligence/npm-packages/react-native-subscription/src/presentation/components/README.md)
-- [Paywall Domain](/Users/umituz/Desktop/github/umituz/apps/artificial_intelligence/npm-packages/react-native-subscription/src/domains/paywall/README.md)

package/src/domains/subscription/presentation/components/sections/SubscriptionSection.md

@@ -1,94 +0,0 @@
-# SubscriptionSection Component
-
-Section component displaying subscription status with details and actions.
-
-## Location
-
-**Import Path**: `@umituz/react-native-subscription`
-
-**File**: `src/presentation/components/sections/SubscriptionSection.tsx`
-
-**Type**: Component
-
-## Strategy
-
-### Subscription Information Display
-
-1. **Status Detection**: Display current subscription status (active/inactive/free)
-2. **Detail Rendering**: Show expiration date, renewal status, product info
-3. **Action Buttons**: Display manage or upgrade button based on status
-4. **Loading States**: Handle loading and error states gracefully
-5. **Translation Support**: Support custom translations for all text
-6. **Visual Hierarchy**: Clear structure with status badge, details, and actions
-
-### Integration Points
-
-- **useSubscriptionStatus**: For subscription status data
-- **usePremium**: For premium status check
-- **DetailRow**: For displaying individual detail items
-- **PremiumStatusBadge**: For status badge display
-- **Navigation**: For manage/upgrade button actions
-
-## Restrictions
-
-### REQUIRED
-
-- **Config Prop**: MUST provide valid subscription config object
-- **Callback Handling**: MUST implement button callbacks
-- **Loading State**: MUST handle loading state in UI
-- **Null Handling**: MUST handle null status values
-
-### PROHIBITED
-
-- **NEVER** display without config data (show loading instead)
-- **NEVER** hardcode status text (use translations)
-- **DO NOT** show both manage and upgrade buttons simultaneously
-- **DO NOT** show buttons for loading state
-
-### CRITICAL SAFETY
-
-- **ALWAYS** handle loading state before displaying data
-- **MUST** validate config object before rendering
-- **ALWAYS** provide clear button labels
-- **NEVER** expose sensitive implementation details
-
-## AI Agent Guidelines
-
-### When Implementing Subscription Sections
-
-1. **Always** provide valid subscription config
-2. **Always** handle loading state
-3. **Always** implement both button callbacks
-4. **Always** use translations for localization
-5. **Never** hardcode status strings
-
-### Integration Checklist
-
-- [ ] Import from correct path: `@umituz/react-native-subscription`
-- [ ] Provide valid subscription config
-- [ ] Implement onUpgradePress callback
-- [ ] Implement onManagePress callback
-- [ ] Handle loading state
-- [ ] Handle null dates
-- [ ] Provide translations for localization
-- [ ] Test with active subscription
-- [ ] Test with expired subscription
-- [ ] Test with free user
-- [ ] Test with lifetime subscription
-
-### Common Patterns
-
-1. **Settings Integration**: Add to settings screen
-2. **Profile Display**: Show in user profile
-3. **Status Card**: Display as standalone card
-4. **With Navigation**: Navigate to detailed management
-5. **Localized Display**: Use with i18n libraries
-6. **Conditional Rendering**: Show/hide based on auth state
-
-## Related Documentation
-
-- **PremiumDetailsCard**: Detailed premium card
-- **DetailRow**: Individual detail item
-- **PremiumStatusBadge**: Status badge component
-- **Subscription Hooks**: `../../hooks/README.md`
-- **Sections README**: `./README.md`

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

@@ -1,31 +0,0 @@
-# Presentation Utils
-
-Utility functions and helpers for the presentation layer.
-
-## Overview
-
-This directory contains utility functions used by presentation components and hooks.
-
-## Contents
-
-- **subscriptionDateUtils.ts** - Date formatting and manipulation for subscription display
-- **paywallUtils.ts** - Paywall-related utility functions
-
-## Date Utilities
-
-### formatDate
-
-Format ISO date string to localized date string.
-
-### calculateDaysRemaining
-
-Calculate days between now and expiration date.
-
-### convertPurchasedAt
-
-Convert purchasedAt date to ISO string.
-
-## Related
-
-- [Hooks](../hooks/README.md)
-- [Types](../types/README.md)

package/src/domains/wallet/README.md

@@ -1,51 +0,0 @@
-# Wallet Domain
-
-Credit balance management, transaction history tracking, and product metadata management.
-
-## Location
-
-`src/domains/wallet/`
-
-## Strategy
-
-Implements layered architecture for credit management with domain layer (entities, value objects, errors), infrastructure layer (repositories, Firebase services, mappers), and presentation layer (hooks, components). Handles initialization, operations, and transaction history with real-time updates.
-
-## Restrictions
-
-### REQUIRED
-
-- All operations require authenticated user
-- Credit operations MUST be validated server-side
-- All credit changes MUST be recorded in transaction history
-- MUST handle insufficient credits gracefully
-
-### PROHIBITED
-
-- MUST NOT allow client-side credit modifications without server validation
-- MUST NOT deduct credits without sufficient balance
-- MUST NOT expose internal repository logic to UI
-- MUST NOT store credit balance in AsyncStorage (use secure backend)
-
-### CRITICAL
-
-- Always validate credit amounts (must be positive)
-- Always implement optimistic updates with rollback
-- Never trust client-side credit balance for security decisions
-- Must implement retry logic for failed operations
-- Always sanitize transaction reasons to prevent injection attacks
-
-## AI Agent Guidelines
-
-When implementing credit operations:
-1. Always check balance before deducting
-2. Always provide transaction reason and metadata
-3. Always handle insufficient credits gracefully
-4. Always implement optimistic updates with rollback
-5. Never trust client-side balance for security
-
-## Related Documentation
-
-- [Credits Repository](infrastructure/README.md)
-- [useCredits Hook](../../presentation/hooks/README.md)
-- [UserCredits Entity](domain/entities/README.md)
-- [Transaction Errors](domain/errors/README.md)

package/src/domains/wallet/domain/README.md

@@ -1,41 +0,0 @@
-# Wallet Domain
-
-## Location
-Wallet domain containing credits and transaction management logic.
-
-## Strategy
-The wallet domain manages user credits, transactions, and credit allocation strategies with duplicate protection, transactional operations, and complete audit trail.
-
-## Restrictions
-
-### REQUIRED
-- Must check credit balance before operations
-- Must handle credit exhaustion gracefully
-- Must track all credit transactions
-- Must reset credits on subscription renewal
-
-### PROHIBITED
-- DO NOT perform operations without balance check
-- DO NOT allow duplicate credit allocations
-- DO NOT skip transaction logging
-- DO NOT bypass credit exhaustion handling
-
-### CRITICAL SAFETY
-- Credit allocations MUST be protected against duplicates
-- All credit operations MUST be transactional
-- Transaction history MUST be complete and accurate
-- Credit exhaustion MUST trigger upgrade flow
-
-## AI Agent Guidelines
-1. Always verify credit balance before performing operations
-2. Handle credit exhaustion with clear upgrade path
-3. Log all credit transactions for audit trail
-4. Implement monthly credit reset on subscription renewal
-5. Test edge cases: zero credits, max credits, duplicates
-6. Use ACCUMULATE mode for renewals, REPLACE for new purchases
-7. Provide optimistic updates with rollback capability
-
-## Related Documentation
-- [Credits README](./README.md)
-- [Credits Entity](./domain/entities/Credits.md)
-- [useCredits Hook](../../presentation/hooks/useCredits.md)

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

@@ -1,41 +0,0 @@
-# Wallet Infrastructure
-
-## Location
-Infrastructure layer for wallet and credits functionality.
-
-## Strategy
-This directory contains implementations for credit persistence, transactions, and credit operations with duplicate protection and optimistic updates.
-
-## Restrictions
-
-### REQUIRED
-- Must check credit balance before deducting
-- Must handle errors appropriately
-- Must use transactions for data consistency
-- Must log all credit operations
-
-### PROHIBITED
-- DO NOT deduct credits without balance check
-- DO NOT allow duplicate credit allocations
-- DO NOT skip transaction boundaries
-- DO NOT ignore credit operation errors
-
-### CRITICAL SAFETY
-- Duplicate allocations MUST be prevented based on purchaseId
-- Credit operations MUST be atomic
-- All operations MUST be logged for debugging
-- Input validation MUST be performed
-
-## AI Agent Guidelines
-1. Always verify credit balance before deduction operations
-2. Implement comprehensive error handling for credit operations
-3. Use transactions to ensure data consistency
-4. Track all credit operations with detailed logging
-5. Test edge cases: zero credits, max credits, duplicates
-6. Validate all input parameters before processing
-7. Implement duplicate protection based on purchaseId
-
-## Related Documentation
-- [Wallet Domain](../domain/README.md)
-- [Credits Entity](../domain/entities/README.md)
-- [useCredits Hook](../../presentation/hooks/useCredits.md)

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

@@ -1,41 +0,0 @@
-# Wallet Presentation Components
-
-## Location
-UI components for wallet and credit display.
-
-## Strategy
-This directory contains React Native components for displaying credits, transactions, and wallet information with clear visual hierarchy and status indicators.
-
-## Restrictions
-
-### REQUIRED
-- Must show loading states appropriately
-- Must provide empty state messages
-- Must allow manual refresh capability
-- Must display transaction history clearly
-
-### PROHIBITED
-- DO NOT hide credit balance from users
-- DO NOT show technical errors directly
-- DO NOT skip loading indicators
-- DO NOT obscure transaction details
-
-### CRITICAL SAFETY
-- Credit balance MUST always be visible
-- Status indicators MUST be color-coded appropriately
-- Transaction history MUST be complete and accurate
-- Purchase links MUST be easily accessible
-
-## AI Agent Guidelines
-1. Emphasize important information with visual hierarchy
-2. Use color coding to indicate status (low/warning/good)
-3. Show skeleton screens while loading data
-4. Provide helpful empty state messages
-5. Allow users to manually refresh credit data
-6. Display complete transaction history
-7. Make credit purchases easily accessible
-
-## Related Documentation
-- [Credit Row](../../../presentation/components/details/CreditRow.md)
-- [Credits Hook](../hooks/README.md)
-- [Wallet Domain](../../domain/README.md)

package/src/domains/wallet/presentation/hooks/README.md

@@ -1,41 +0,0 @@
-# Wallet Presentation Hooks
-
-## Location
-React hooks for wallet and credit functionality.
-
-## Strategy
-This directory contains React hooks specifically for credit management and wallet operations with optimistic updates and proper error handling.
-
-## Restrictions
-
-### REQUIRED
-- Must check balance before deducting
-- Must handle loading states appropriately
-- Must handle deduction failures gracefully
-- Must log all credit operations
-
-### PROHIBITED
-- DO NOT deduct credits without balance check
-- DO NOT skip error handling
-- DO NOT ignore loading states
-- DO NOT perform operations without tracking
-
-### CRITICAL SAFETY
-- Balance checks MUST precede all deductions
-- Deduction failures MUST be handled gracefully
-- Optimistic updates MUST support rollback
-- All operations MUST be logged
-
-## AI Agent Guidelines
-1. Always check credit balance before deducting
-2. Show appropriate loading states during operations
-3. Handle deduction failures with graceful recovery
-4. Use optimistic updates for better user experience
-5. Log all credit operations for debugging
-6. Initialize credits automatically after premium purchase
-7. Test edge cases: zero credits, max credits, failures
-
-## Related Documentation
-- [useCredits Hook Documentation](../../../presentation/hooks/useCredits.md)
-- [useDeductCredit Hook Documentation](../../../presentation/hooks/useDeductCredit.md)
-- [Credits Entity](../../domain/entities/README.md)

package/src/shared/application/ports/README.md

@@ -1,48 +0,0 @@
-# Application Ports
-
-Interfaces defining contracts between application layer and external dependencies.
-
-## Location
-
-`src/application/ports/`
-
-## Strategy
-
-Port interfaces define how the application layer interacts with external services and repositories, enabling dependency inversion and testability through clear contracts.
-
-## Restrictions
-
-### REQUIRED
-
-- MUST use interface segregation (keep interfaces focused)
-- MUST document behavior thoroughly
-- MUST use domain entities in return types
-- MUST make all I/O operations async
-- MUST define clear contracts between layers
-
-### PROHIBITED
-
-- MUST NOT couple interfaces to specific implementations
-- MUST NOT include infrastructure concerns in port definitions
-- MUST NOT leak implementation details through interfaces
-
-### CRITICAL
-
-- Keep interfaces focused and segregated
-- Document all behavior thoroughly
-- Use domain entities in return types
-- Ensure all I/O operations are async
-
-## AI Agent Guidelines
-
-When working with application ports:
-1. Interface Segregation - keep interfaces focused
-2. Clear Contracts - document behavior thoroughly
-3. Return Types - use domain entities in return types
-4. Async Operations - all I/O operations should be async
-
-## Related Documentation
-
-- [Application Layer](../README.md)
-- [Infrastructure Services](../../infrastructure/services/README.md)
-- [Infrastructure Repositories](../../infrastructure/repositories/README.md)