@umituz/react-native-subscription 2.37.39 → 2.37.40

package/src/utils/packageTypeDetector.ts

@@ -1,27 +1,12 @@
-/**
- * Package Type Detector
- * Detects subscription package type from RevenueCat package identifier
- */
-
 import { PACKAGE_TYPE, type PackageType } from "../domains/subscription/core/SubscriptionConstants";
 
 export type SubscriptionPackageType = PackageType;
 
-/**
- * Check if identifier is a credit package (consumable purchase)
- * Credit packages use a different system and don't need type detection
- */
 export function isCreditPackage(identifier: string): boolean {
   if (!identifier) return false;
-  // Matches "credit" as a word or part of a common naming pattern
-  // More strict to avoid false positives (e.g. "accredited")
   return /(?:^|[._-])credit(?:$|[._-])/i.test(identifier);
 }
 
-/**
- * Detect package type from product identifier
- * Supports common RevenueCat naming patterns with regex for better accuracy
- */
 export function detectPackageType(productIdentifier: string): SubscriptionPackageType {
   if (!productIdentifier) {
     return PACKAGE_TYPE.UNKNOWN;
@@ -29,27 +14,22 @@ export function detectPackageType(productIdentifier: string): SubscriptionPackag
 
   const normalized = productIdentifier.toLowerCase();
 
-  // Skip credit packages silently - they use creditPackageConfig instead
   if (isCreditPackage(normalized)) {
     return PACKAGE_TYPE.UNKNOWN;
   }
 
-  // Weekly detection: matches "weekly" or "week" as distinct parts of the ID
   if (/\bweekly?\b|_week_|-week-|\.week\./i.test(normalized)) {
     return PACKAGE_TYPE.WEEKLY;
   }
 
-  // Monthly detection: matches "monthly" or "month"
   if (/\bmonthly?\b|_month_|-month-|\.month\./i.test(normalized)) {
     return PACKAGE_TYPE.MONTHLY;
   }
 
-  // Yearly detection: matches "yearly", "year", or "annual"
   if (/\byearly?\b|_year_|-year-|\.year\.|annual/i.test(normalized)) {
     return PACKAGE_TYPE.YEARLY;
   }
-  
-  // Lifetime detection: matches "lifetime"
+
   if (/\blifetime\b|_lifetime_|-lifetime-|\.lifetime\./i.test(normalized)) {
       return PACKAGE_TYPE.LIFETIME;
   }

package/src/utils/premiumStatusUtils.ts

@@ -1,27 +1,14 @@
-/**
- * Premium Status Utilities
- *
- * Core premium status determination logic
- */
-
 import type { PremiumStatusFetcher } from './types';
 
-
-/**
- * Get isPremium value with centralized logic
- */
 export function getIsPremium(
   isAnonymous: boolean,
   userId: string | null,
   isPremiumOrFetcher: boolean | PremiumStatusFetcher,
 ): Promise<boolean> {
-  // Anonymous users NEVER have premium
   if (isAnonymous || userId === null) return Promise.resolve(false);
 
-  // Sync mode: return the provided isPremium value
   if (typeof isPremiumOrFetcher === 'boolean') return Promise.resolve(isPremiumOrFetcher);
 
-  // Async mode: fetch premium status
   return (async () => {
     try {
       return await isPremiumOrFetcher.isPremium(userId!);
@@ -31,4 +18,4 @@ export function getIsPremium(
       );
     }
   })();
-}
+}

package/src/utils/priceUtils.ts

@@ -1,14 +1,3 @@
-/**
- * Price Formatting Utilities
- * Apple App Store Guideline 3.1.2 Compliance
- */
-
-/**
- * Format price for display
- * @param price - Price value
- * @param currencyCode - Currency code (e.g., 'USD', 'EUR')
- * @returns Formatted price string
- */
 export function formatPrice(price: number, currencyCode: string): string {
   try {
     return new Intl.NumberFormat('en-US', {
@@ -28,35 +17,11 @@ const PERIOD_SUFFIX_MAP: Record<string, string> = {
   yearly: '/year',
 };
 
-/**
- * Extract billing period suffix from package identifier
- * Apple App Store Guideline 3.1.2 Compliance:
- * - Displays billing frequency clearly and conspicuously
- * - Format: /week, /month, /year
- *
- * @param identifier - RevenueCat package identifier (e.g., "$rc_weekly", "$rc_monthly", "$rc_annual")
- * @returns Billing period suffix (e.g., "/week", "/month", "/year") or empty string
- */
 export function getBillingPeriodSuffix(identifier: string): string {
   const packageType = detectPackageType(identifier);
   return PERIOD_SUFFIX_MAP[packageType] ?? '';
 }
 
-/**
- * Format price with billing period
- * Apple App Store Guideline 3.1.2 Compliance:
- * - Combines price with billing frequency for clear display
- * - Format: $2.99/week, $14.99/month, $39.99/year
- *
- * RevenueCat Best Practice:
- * - Follows recommended price_per_period format
- * - Clear and conspicuous billing frequency display
- *
- * @param price - Price value
- * @param currencyCode - Currency code (e.g., 'USD', 'EUR')
- * @param identifier - RevenueCat package identifier
- * @returns Formatted price with billing period (e.g., "$2.99/week")
- */
 export function formatPriceWithPeriod(
   price: number,
   currencyCode: string,

package/src/utils/tierUtils.ts

@@ -1,12 +1,5 @@
-/**
- * User Tier Core Utilities
- *
- * Core logic for determining user tier and premium status
- */
-
 import { USER_TIER, type UserTierInfo } from './types';
 
-
 export function getUserTierInfo(
   isAnonymous: boolean,
   userId: string | null,
@@ -38,4 +31,4 @@ export function checkPremiumAccess(
 ): boolean {
   if (isAnonymous || userId === null) return false;
   return isPremium;
-}
+}

package/src/utils/types.ts

@@ -1,40 +1,16 @@
-/**
- * User Tier Types
- *
- * Type definitions for user tier system
- */
-
 import { USER_TIER, type UserTierType } from '../domains/subscription/core/SubscriptionConstants';
 
 export type UserTier = UserTierType;
 export { USER_TIER };
 
 export interface UserTierInfo {
-  /** User tier classification */
   tier: UserTier;
-
-  /** Whether user has premium access */
   isPremium: boolean;
-
-  /** Whether user is anonymous (not authenticated) */
   isAnonymous: boolean;
-
-  /** Whether user is authenticated */
   isAuthenticated: boolean;
-
-  /** User ID (null for anonymous users) */
   userId: string | null;
 }
 
-/**
- * Premium status fetcher interface
- * Apps should implement this to provide premium status from their database
- */
 export interface PremiumStatusFetcher {
-  /**
-   * Check if user has active premium subscription
-   * @param userId - User ID (never null, this is only called for authenticated users)
-   * @returns Promise<boolean> - Whether user has premium subscription
-   */
   isPremium(userId: string): Promise<boolean>;
-}
+}

package/src/utils/validation.ts

@@ -1,9 +1,3 @@
-/**
- * User Tier Validation Utilities
- *
- * Type guards and validation functions for user tier system
- */
-
 import { USER_TIER, type UserTier, type UserTierInfo } from './types';
 
 export function isValidUserTier(value: unknown): value is UserTier {
@@ -20,4 +14,4 @@ export function isUserTierInfo(value: unknown): value is UserTierInfo {
     typeof obj.isAuthenticated === 'boolean' &&
     (obj.userId === null || typeof obj.userId === 'string')
   );
-}
+}

package/src/domains/README.md

@@ -1,52 +0,0 @@
-# Domains
-
-Specialized domain modules implementing specific business logic and features.
-
-## Location
-
-`src/domains/`
-
-## Strategy
-
-Implements Domain-Driven Design (DDD) principles with self-contained domains. Each domain includes domain layer (business logic, entities, value objects), infrastructure layer (external integrations, repositories), and presentation layer (domain-specific hooks and components).
-
-## Restrictions
-
-### REQUIRED
-
-- Domains MUST NOT directly depend on each other
-- MUST use well-defined interfaces between layers
-- MUST depend on abstractions, not concretions (Dependency Inversion)
-- All domains MUST be testable in isolation
-
-### PROHIBITED
-
-- MUST NOT share domain logic between domains (use shared kernel if needed)
-- MUST NOT create circular dependencies between domains
-- MUST NOT bypass domain layer from presentation
-- MUST NOT expose infrastructure details to other domains
-
-### CRITICAL
-
-- Always validate invariants at domain boundaries
-- Always implement domain errors for business rule violations
-- Never allow inconsistent domain state
-- Must implement proper transaction boundaries
-- Always sanitize inputs from external sources
-
-## AI Agent Guidelines
-
-When working with domains:
-1. Always respect domain boundaries
-2. Always use dependency inversion
-3. Always implement domain-specific errors
-4. Always validate invariants at boundaries
-5. Never create circular dependencies
-
-## Related Documentation
-
-- [Wallet Domain](wallet/README.md)
-- [Paywall Domain](paywall/README.md)
-- [Config Domain](config/README.md)
-- [Domain Layer](../domain/README.md)
-- [Infrastructure](../infrastructure/README.md)

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

@@ -1,37 +0,0 @@
-# Config Domain
-
-## Location
-Domain layer for configuration management.
-
-## Strategy
-This directory contains the business logic and domain models for subscription and feature configuration.
-
-## Restrictions
-
-### REQUIRED
-- Must use entities for domain models
-- Must validate in constructor
-- Must keep entities immutable
-
-### PROHIBITED
-- DO NOT bypass entity validation
-- DO NOT mutate entities after creation
-- DO NOT leak domain logic to application layer
-
-### CRITICAL SAFETY
-- All business rules MUST be enforced in entities
-- Validation failures MUST fail fast
-- Type safety MUST be maintained at compile time
-
-## AI Agent Guidelines
-1. When creating new configurations, use existing entities
-2. Always validate configuration data through entity constructors
-3. Encapsulate business logic within domain entities
-4. Implement proper equality methods for value objects
-5. Provide formatting methods for display purposes
-6. Maintain strict type safety with TypeScript
-
-## Related Documentation
-- [Config Domain](../../README.md)
-- [Config Entities](./entities/README.md)
-- [Config Value Objects](./value-objects/README.md)

package/src/domains/config/domain/entities/README.md

@@ -1,41 +0,0 @@
-# Config Domain Entities
-
-## Location
-Domain entities for configuration management.
-
-## Strategy
-This directory contains entity classes representing configuration concepts like packages, features, and paywalls with strict validation and immutability.
-
-## Restrictions
-
-### REQUIRED
-- Must validate all configuration in constructor
-- Must treat entities as immutable
-- Must provide clear error messages
-- Must use TypeScript strict mode
-
-### PROHIBITED
-- DO NOT modify entities after creation
-- DO NOT bypass validation logic
-- DO NOT expose mutable internal state
-- DO NOT allow invalid configuration
-
-### CRITICAL SAFETY
-- All validation MUST happen in constructor
-- Entities MUST fail fast on invalid input
-- Error messages MUST be descriptive
-- Factory functions MUST provide valid defaults
-
-## AI Agent Guidelines
-1. Always validate configuration data in entity constructors
-2. Treat all entities as immutable values
-3. Keep business logic encapsulated within entities
-4. Provide factory functions for common configurations
-5. Test validation logic thoroughly
-6. Use TypeScript strict types for all properties
-7. Return descriptive error messages for validation failures
-
-## Related Documentation
-- [Config Domain](../README.md)
-- [Config Value Objects](../value-objects/README.md)
-- [Config Utils](../../utils/README.md)

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)