Skip to content

Component Name: membershipWizardTest

Last Updated: 2025-09-29 Source Code: https://bitbucket.org/i2cinc/i2c.salesforce.metadata/src/STAGING/force-app/main/default/lwc/membershipWizardTest

API Name: c-membershipWizardTest Type: Page Component (Multi-step Wizard) Target: Community pages

Business Purpose

Multi-step membership purchase and renewal wizard. Guides users through selecting membership type, adding community products, entering demographics, setting up auto-renewal, providing payment information, and completing purchase. Critical component for member acquisition and retention.

Component Structure

Note: Component is extremely large (28,085 tokens, could not fully read). Based on naming and common patterns:

Likely Features

  • Multi-step wizard interface (5-10 steps)
  • Membership type selection
  • Community product add-ons
  • Demographics collection
  • Auto-renewal opt-in/opt-out
  • Payment method entry
  • Order summary/review
  • Confirmation step
  • Progress indicator
  • Back/Next navigation
  • Form validation at each step
  • Shopping cart integration
  • Payment processing integration

Likely Dependencies

  • Apex: ProductController, CartController, PaymentController, AccountController
  • Child Components: Many (c-formInput, c-confirmationModal, c-reCaptcha, etc.)
  • Commerce APIs
  • Payment Gateway integration
  • Custom Objects: Order, Cart, Product, Subscription

Usage

<!-- Membership purchase/renewal page -->
<c-membership-wizard-test></c-membership-wizard-test>

⚠️ Pre-Go-Live Concerns

CRITICAL

  • Extremely large file: 28K+ tokens suggests component should be refactored into smaller sub-components
  • Complex state management: Multi-step wizards prone to state bugs
  • Payment processing: Any bugs could cause failed transactions or security issues

HIGH

  • No unit tests: Given criticality and size, must have comprehensive test coverage
  • Likely performance issues: Large component may have slow initial render

Maintenance Notes

Complexity: Extremely High Key Notes: - CRITICAL: Component is extremely large and complex - highest priority for refactoring - Core business function (membership sales) - Likely handles payment processing (PCI considerations) - Multi-step wizard pattern requires careful state management - Should be broken into smaller components: - Step 1: Membership Selection - Step 2: Product Add-ons - Step 3: Demographics - Step 4: Auto-Renewal - Step 5: Payment - Step 6: Review - Step 7: Confirmation - Each step should be its own component - Consider using Lightning Flow instead for easier maintenance - High business impact - any bugs affect revenue - Must be thoroughly tested before any changes

Browser Compatibility: - Requires modern browser (payment integration) - Mobile: Must support mobile purchase flow