Livewire Combined Request Laravel Package

Product Decisions This Supports

• DRY Validation Logic: Eliminates duplicate validation rules between Livewire components and HTTP/API controllers, reducing technical debt and maintenance overhead.
• Unified Authorization: Centralizes authorization logic in a single place, ensuring consistency across all request contexts (APIs, Livewire, and traditional HTTP routes).
• Accelerated Development: Speeds up feature delivery by reusing validation logic for both backend APIs and frontend components, aligning with Laravel’s "convention over configuration" philosophy.
• Livewire 3/4 Adoption: Enables seamless integration of Livewire components with Laravel’s FormRequest ecosystem, bridging the gap between traditional Laravel validation and Livewire’s reactive paradigm.
• Route Model Binding Consistency: Maintains Laravel’s route model binding behavior in Livewire contexts, reducing cognitive load for developers familiar with Laravel’s routing system.
• Scalable Architecture: Supports complex applications with nested validation, parameter requirements, and dynamic authorization, making it ideal for enterprise-grade Laravel projects.
• Build vs. Buy Decision: Avoids reinventing validation logic or relying on third-party solutions (e.g., custom middleware or ad-hoc validation in components), reducing dependency risks.

When to Consider This Package

• Avoid if:
  • Your project uses Livewire 2 or Laravel <10, as compatibility is limited to Livewire 3/4 and Laravel 10+.
  • You prioritize minimalism and prefer writing validation separately for APIs and Livewire (e.g., small projects with simple forms).
  • Your team lacks familiarity with Laravel’s FormRequest system, as this package assumes existing knowledge of validation rules, authorization, and route binding.
  • You need highly customized validation that cannot be expressed in a single FormRequest (e.g., context-specific rules that vary drastically between APIs and Livewire).
  • Your application relies on third-party validation libraries that conflict with Laravel’s native validation system.
• Consider if:
  • You’re building a Laravel + Livewire application with shared validation needs (e.g., forms that update both a database record and a real-time UI).
  • Your team follows DRY principles and wants to avoid duplicating validation logic across controllers and components.
  • You need consistent authorization across APIs and Livewire components (e.g., role-based access control for CRUD operations).
  • Your project involves complex parameter handling, such as route model binding in APIs and manual injection in Livewire.
  • You’re adopting Livewire 3/4 and want to leverage Laravel’s mature validation ecosystem without sacrificing Livewire’s reactivity.

How to Pitch It (Stakeholders)

For Executives: "This package eliminates redundant validation code—saving development time and reducing bugs—by unifying Laravel’s FormRequest validation across APIs and Livewire components. For example, a team updating a profile in both a REST API and a Livewire form will now use a single validation rule set, cutting maintenance costs by 30%+ while ensuring consistency. It’s a low-risk, high-reward tool that aligns with our Laravel/Livewire stack and accelerates feature delivery."

For Engineers: *"This solves the classic ‘validation duplication’ problem in Laravel/Livewire apps. Instead of copying-pasting rules between controllers and components, we write them once in a CombinedFormRequest and reuse them everywhere. Key benefits:

• Automatic parameter validation: Define required params (e.g., team, workspace) once; they’re validated in both HTTP and Livewire contexts.
• Unified authorization: Your authorize() method works identically in APIs and Livewire.
• Seamless Livewire integration: Use validateLivewire() with your component’s properties, and it handles camelCase ↔ snake_case conversion (optional).
• Zero config: Drop it into any Laravel 10+/Livewire 3/4 app—no service providers or complex setup. Perfect for projects where forms update both a database and a real-time UI, like dashboards or admin panels."

For Product Managers: *"This reduces technical debt by centralizing validation logic, which is critical for long-term maintainability. It also enables faster iteration: when business rules change (e.g., ‘only admins can update teams’), we update one FormRequest instead of hunting down duplicates in controllers and components. Ideal for features like:

• User profiles (API + Livewire sync).
• Team/workspace management (shared validation for CRUD operations).
• Forms with complex rules (e.g., conditional validation, nested objects). Think of it as ‘validation as a service’ for your Laravel/Livewire app."