@3fn/core 14.0.0 → 15.0.0

package/src/components/core/Input-Text-Email/stateManagement.ts

@@ -1,160 +0,0 @@
-/**
- * Input-Text-Email State Management
- * 
- * Extends Input-Text-Base state management with email-specific validation.
- * Handles email validation on blur and state transitions.
- * 
- * Stemma System: Form Inputs Family
- * Component Type: Semantic (inherits from Input-Text-Base)
- * Naming Convention: [Family]-[Type]-[Variant] = Input-Text-Email
- * 
- * State Machine (extends Input-Text-Base):
- * - All Input-Text-Base states apply
- * - Email validation triggers on blur
- * - Error state set when email format is invalid
- * 
- * Behavioral Contracts:
- * - validates_email_format: Validates email against RFC 5322 pattern
- * - provides_email_autocomplete: Enables browser email autofill
- * - inherits_all_input_text_base_contracts: All base contracts apply
- * 
- * Requirements: R4.3
- */
-
-import { InputTextEmailProps, InputTextEmailState, EmailValidationResult } from './types';
-import { validateEmail, DEFAULT_INVALID_EMAIL_MESSAGE } from './validation';
-import {
-  createInitialState as createBaseInitialState,
-  handleFocus as handleBaseFocus,
-  handleBlur as handleBaseBlur,
-  handleValueChange as handleBaseValueChange
-} from '../Input-Text-Base/stateManagement';
-
-/**
- * Create Initial State for Input-Text-Email
- * 
- * Creates the initial component state based on props.
- * Extends Input-Text-Base initial state with email-specific fields.
- * 
- * @param props - Component props
- * @returns Initial state
- */
-export function createInitialState(props: InputTextEmailProps): InputTextEmailState {
-  const baseState = createBaseInitialState({
-    ...props,
-    type: 'email',
-    autocomplete: 'email'
-  });
-  
-  return {
-    ...baseState,
-    isEmailValid: true, // Assume valid until validated
-    hasBeenValidated: false
-  };
-}
-
-/**
- * Handle Focus Event
- * 
- * Updates state when input receives focus.
- * Delegates to Input-Text-Base focus handler.
- * 
- * @param currentState - Current component state
- * @returns Updated state
- */
-export function handleFocus(currentState: InputTextEmailState): InputTextEmailState {
-  const baseState = handleBaseFocus(currentState);
-  
-  return {
-    ...currentState,
-    ...baseState
-  };
-}
-
-/**
- * Handle Blur Event with Email Validation
- * 
- * Updates state when input loses focus.
- * Triggers email validation on blur.
- * 
- * @param currentState - Current component state
- * @param value - Current input value
- * @param customValidator - Optional custom validation function
- * @param invalidEmailMessage - Optional custom error message
- * @returns Updated state with validation result
- */
-export function handleBlur(
-  currentState: InputTextEmailState,
-  value: string,
-  customValidator?: (email: string) => boolean,
-  invalidEmailMessage?: string
-): InputTextEmailState {
-  const baseState = handleBaseBlur(currentState);
-  
-  // Validate email on blur
-  const validationResult = validateEmail(value, customValidator, invalidEmailMessage);
-  
-  return {
-    ...currentState,
-    ...baseState,
-    isEmailValid: validationResult.isValid,
-    hasBeenValidated: true,
-    hasError: !validationResult.isValid || currentState.hasError
-  };
-}
-
-/**
- * Handle Value Change
- * 
- * Updates state when input value changes.
- * Clears validation error when user starts typing again.
- * 
- * @param currentState - Current component state
- * @param newValue - New input value
- * @returns Updated state
- */
-export function handleValueChange(
-  currentState: InputTextEmailState,
-  newValue: string
-): InputTextEmailState {
-  const baseState = handleBaseValueChange(currentState, newValue);
-  
-  // Clear email validation error when user starts typing
-  // (will be re-validated on blur)
-  return {
-    ...currentState,
-    ...baseState,
-    // Keep hasBeenValidated but clear the error state while typing
-    hasError: false,
-    isEmailValid: true
-  };
-}
-
-/**
- * Get Email Validation Error Message
- * 
- * Returns the appropriate error message based on validation state.
- * 
- * @param state - Current component state
- * @param propsErrorMessage - Error message from props (takes precedence)
- * @param invalidEmailMessage - Custom invalid email message
- * @returns Error message to display, or undefined if no error
- */
-export function getEmailErrorMessage(
-  state: InputTextEmailState,
-  propsErrorMessage?: string,
-  invalidEmailMessage?: string
-): string | undefined {
-  // Props error message takes precedence
-  if (propsErrorMessage) {
-    return propsErrorMessage;
-  }
-  
-  // Show email validation error if validated and invalid
-  if (state.hasBeenValidated && !state.isEmailValid) {
-    return invalidEmailMessage || DEFAULT_INVALID_EMAIL_MESSAGE;
-  }
-  
-  return undefined;
-}
-

package/src/components/core/Input-Text-Email/tokens.ts

@@ -1,33 +0,0 @@
-/**
- * Input-Text-Email Component Token References
- * 
- * Inherits all tokens from Input-Text-Base.
- * Email-specific components use the same visual tokens as the base component.
- * 
- * Stemma System: Form Inputs Family
- * Component Type: Semantic (inherits from Input-Text-Base)
- * Naming Convention: [Family]-[Type]-[Variant] = Input-Text-Email
- * 
- * Token Inheritance:
- * Input-Text-Email inherits ALL tokens from Input-Text-Base.
- * No additional tokens are required for email-specific functionality.
- * 
- * This file re-exports Input-Text-Base tokens for consistency and
- * to allow future email-specific token additions if needed.
- */
-
-// Re-export all tokens from Input-Text-Base
-export {
-  typographyTokens,
-  colorTokens,
-  spacingTokens,
-  motionTokens,
-  borderTokens,
-  accessibilityTokens,
-  blendTokens,
-  inputTextBaseTokens
-} from '../Input-Text-Base/tokens';
-
-// Alias for semantic naming
-export { inputTextBaseTokens as inputTextEmailTokens } from '../Input-Text-Base/tokens';
-

package/src/components/core/Input-Text-Email/types.ts

@@ -1,72 +0,0 @@
-/**
- * Input-Text-Email Component Types
- * 
- * Defines the public API and internal state interfaces for the Input-Text-Email component
- * across all platforms (web, iOS, Android).
- * 
- * Stemma System: Form Inputs Family
- * Component Type: Semantic (inherits from Input-Text-Base)
- * Naming Convention: [Family]-[Type]-[Variant] = Input-Text-Email
- */
-
-import { InputTextBaseProps, InputTextBaseState } from '../Input-Text-Base/types';
-
-/**
- * Input-Text-Email Component Props
- * 
- * Extends Input-Text-Base props with email-specific functionality.
- * The type and autocomplete properties are fixed for email input.
- */
-export interface InputTextEmailProps extends Omit<InputTextBaseProps, 'type' | 'autocomplete'> {
-  /** 
-   * Input type is fixed to 'email' for this semantic component.
-   * This ensures proper keyboard and validation behavior across platforms.
-   */
-  readonly type?: 'email';
-  
-  /** 
-   * Autocomplete is fixed to 'email' for browser autofill support.
-   * This enables email address suggestions from the browser.
-   */
-  readonly autocomplete?: 'email';
-  
-  /**
-   * Custom email validation function.
-   * If not provided, uses the default RFC 5322 compliant email regex.
-   * Return true if valid, false if invalid.
-   */
-  customValidator?: (email: string) => boolean;
-  
-  /**
-   * Custom error message for invalid email format.
-   * If not provided, uses the default "Please enter a valid email address".
-   */
-  invalidEmailMessage?: string;
-}
-
-/**
- * Input-Text-Email State
- * 
- * Extends Input-Text-Base state with email-specific validation state.
- */
-export interface InputTextEmailState extends InputTextBaseState {
-  /** Whether the email format is valid */
-  isEmailValid: boolean;
-  
-  /** Whether validation has been triggered (on blur) */
-  hasBeenValidated: boolean;
-}
-
-/**
- * Email Validation Result
- * 
- * Result of email validation including validity and error message.
- */
-export interface EmailValidationResult {
-  /** Whether the email is valid */
-  isValid: boolean;
-  
-  /** Error message if invalid, undefined if valid */
-  errorMessage?: string;
-}
-

package/src/components/core/Input-Text-Email/validation.ts

@@ -1,130 +0,0 @@
-/**
- * Input-Text-Email Validation
- * 
- * Email validation logic for the Input-Text-Email component.
- * Implements RFC 5322 compliant email validation with practical considerations.
- * 
- * Stemma System: Form Inputs Family
- * Component Type: Semantic (inherits from Input-Text-Base)
- * Naming Convention: [Family]-[Type]-[Variant] = Input-Text-Email
- * 
- * Behavioral Contracts:
- * - validates_email_format: Validates email against RFC 5322 pattern
- * - provides_email_autocomplete: Enables browser email autofill
- * - inherits_all_input_text_base_contracts: All base contracts apply
- * 
- * Requirements: R4.3 (Input-Text-Email validation and autocomplete)
- */
-
-import { EmailValidationResult } from './types';
-
-/**
- * Default error message for invalid email format.
- */
-export const DEFAULT_INVALID_EMAIL_MESSAGE = 'Please enter a valid email address';
-
-/**
- * RFC 5322 compliant email regex pattern.
- * 
- * This pattern validates:
- * - Local part: alphanumeric, dots, hyphens, underscores, plus signs
- * - @ symbol
- * - Domain part: alphanumeric, dots, hyphens
- * - TLD: 2+ characters
- * 
- * Note: This is a practical implementation that covers 99%+ of valid emails
- * while rejecting obviously invalid formats. It's not a complete RFC 5322
- * implementation (which would be extremely complex) but balances accuracy
- * with usability.
- */
-export const EMAIL_REGEX = /^[a-zA-Z0-9.!#$%&'*+/=?^_`{|}~-]+@[a-zA-Z0-9](?:[a-zA-Z0-9-]{0,61}[a-zA-Z0-9])?(?:\.[a-zA-Z0-9](?:[a-zA-Z0-9-]{0,61}[a-zA-Z0-9])?)*$/;
-
-/**
- * Validate email format using the default RFC 5322 pattern.
- * 
- * @param email - The email address to validate
- * @returns true if the email format is valid, false otherwise
- * 
- * Requirements: R4.3
- */
-export function isValidEmail(email: string): boolean {
-  // Empty strings are not validated (use required prop for that)
-  if (!email || email.trim() === '') {
-    return true;
-  }
-  
-  const trimmedEmail = email.trim();
-  
-  // Check basic regex pattern first
-  if (!EMAIL_REGEX.test(trimmedEmail)) {
-    return false;
-  }
-  
-  // Additional RFC 5322 checks for dots in local part
-  const localPart = trimmedEmail.split('@')[0];
-  
-  // Local part cannot start with a dot
-  if (localPart.startsWith('.')) {
-    return false;
-  }
-  
-  // Local part cannot end with a dot
-  if (localPart.endsWith('.')) {
-    return false;
-  }
-  
-  // Local part cannot have consecutive dots
-  if (localPart.includes('..')) {
-    return false;
-  }
-  
-  return true;
-}
-
-/**
- * Validate email and return a result object with validity and error message.
- * 
- * @param email - The email address to validate
- * @param customValidator - Optional custom validation function
- * @param invalidEmailMessage - Optional custom error message
- * @returns EmailValidationResult with isValid and optional errorMessage
- * 
- * Requirements: R4.3
- */
-export function validateEmail(
-  email: string,
-  customValidator?: (email: string) => boolean,
-  invalidEmailMessage?: string
-): EmailValidationResult {
-  // Empty strings are valid (use required prop for empty validation)
-  if (!email || email.trim() === '') {
-    return { isValid: true };
-  }
-  
-  // Use custom validator if provided, otherwise use default
-  const validator = customValidator || isValidEmail;
-  const isValid = validator(email);
-  
-  if (isValid) {
-    return { isValid: true };
-  }
-  
-  return {
-    isValid: false,
-    errorMessage: invalidEmailMessage || DEFAULT_INVALID_EMAIL_MESSAGE
-  };
-}
-
-/**
- * Normalize email address for consistent handling.
- * 
- * - Trims whitespace
- * - Converts to lowercase (email addresses are case-insensitive)
- * 
- * @param email - The email address to normalize
- * @returns Normalized email address
- */
-export function normalizeEmail(email: string): string {
-  return email.trim().toLowerCase();
-}
-