- What Laravel versions does baskooijmaninc/suzie support, and how do I check compatibility?
- The package targets Laravel 8+ but lacks explicit version constraints in its documentation. Run `composer why-not baskooijmaninc/suzie` to verify compatibility with your stack. If conflicts arise, check the package’s PHP version requirements (likely 8.0+) and manually test core features like form validation and ORM integration.
- Does Suzie require Bootstrap 5 or Bootstrap 3 for form validation styling?
- Suzie uses Bootstrap 5 for forms but relies on Bootstrap 3 CSS classes for validation styling (e.g., `.has-feedback`). You must include the provided CSS snippet in your project to ensure validation feedback (success/warning/error states) renders correctly. This is explicitly documented in the setup section.
- How do I integrate Suzie’s ORM and FormBuilder into a Laravel project?
- Install via Composer (`composer require baskooijmaninc/suzie`), then register the service provider in `config/app.php`. The package likely expects you to bind its core classes (e.g., `SuzieORM`, `SuzieFormBuilder`) in `AppServiceProvider::boot()` using Laravel’s container. Check the README for publishable config files or facade setup.
- Are there known issues with PHP 8.1+ or Laravel 10+ compatibility?
- The package’s GitHub activity and documentation are sparse, so test thoroughly with your PHP/Laravel version. If you encounter type errors (e.g., strict typing conflicts), check for unresolved issues or fork the repo to patch compatibility. Start with a minimal test case (e.g., a single form) before full integration.
- Can Suzie replace Laravel’s built-in validation or FormRequest classes?
- Suzie provides a FormBuilder with Bootstrap 3 validation styling, but it doesn’t replace Laravel’s validation system. Use it for UI feedback (e.g., inline error messages) while keeping Laravel’s validation logic (e.g., `FormRequest` rules) intact. The package likely wraps existing validation results for styling purposes.
- What’s the fallback if Suzie is abandoned or unmaintained?
- Fork the repository to patch critical issues or extract its core logic (e.g., form styling CSS, ORM helpers) into your project. Since it’s MIT-licensed, you can modify it freely. Document the fork in your `composer.json` under `repositories` to avoid dependency risks.
- Does Suzie support Livewire or Inertia.js for dynamic forms?
- The package focuses on server-side form rendering with Bootstrap 5/3. For Livewire/Inertia, manually adapt Suzie’s form classes to your frontend framework’s requirements (e.g., wire:model bindings). Test validation feedback in both client-side and server-side scenarios, as Suzie’s CSS relies on traditional form submission patterns.
- How do I test Suzie’s form validation and ORM features in Laravel?
- Write PHPUnit tests targeting Suzie’s public methods (e.g., `SuzieFormBuilder::create()`). Mock Laravel’s validation facade if needed. For ORM tests, use Laravel’s database testing tools (`createTestingDatabase`) and verify Suzie’s query builders interact correctly with Eloquent models. Add edge cases like multibyte strings if locale-sensitive.
- Are there alternatives to Suzie for Laravel form handling?
- Consider `laravelcollective/html` for Bootstrap forms, `spatie/laravel-form-builder` for dynamic forms, or Laravel’s native `FormRequest` + Blade for validation. Suzie’s unique value is its Bootstrap 3 validation styling for Bootstrap 5 forms—if you don’t need this, built-in tools may suffice.
- Does Suzie modify global state (e.g., setlocale) that could affect multi-tenant apps?
- The package’s documentation doesn’t mention global state modifications, but always test in a multi-tenant environment. If Suzie alters locale settings or session data, isolate its usage to specific services or middleware to avoid cross-tenant conflicts. Check for undocumented static properties or singleton behaviors.