Weave Code
RAD related functionality for usage in Symfony.
Frequently asked questions about Rad Bundle
- Can I use `becklyn/rad-bundle` directly in Laravel, or do I need to rewrite components?
- The bundle is Symfony-focused, so direct use in Laravel isn’t recommended. However, its AJAX protocol and form extensions can be adapted. For example, replace the `AjaxResponseBuilder` with a Laravel middleware or trait, and replicate form collections using Laravel Collective or custom Blade components. Prioritize modular adoption for high ROI components like AJAX.
- How do I implement the AJAX protocol in Laravel to match `becklyn/rad-bundle`'s `AjaxResponse` interface?
- Create a middleware (e.g., `AjaxResponseMiddleware`) to standardize responses. Use Laravel’s `Response::json()` to mirror the `ok`, `status`, `data`, and `message` fields. For frontend compatibility, pair it with a Laravel frontend adapter like `laravel-vue-frontend` or ensure your TypeScript client (e.g., `mojave`) aligns with the interface.
- Are there Laravel alternatives to the form collection extensions (e.g., `empty_message`, `entry_add_label`)?
- Yes. Use Laravel Collective’s `html` package for basic collection fields, then extend with custom Blade directives or JavaScript for dynamic labels. For example, wrap the `add`/`remove` buttons in Blade components with inline labels. Avoid tight Symfony dependencies like `BundleExtension`—Laravel’s service container handles this differently.
- Will the `SimpleEntitySearchHelper` work with Laravel’s Eloquent, or do I need a custom solution?
- The helper relies on Doctrine’s `JSON_SEARCH()`, which isn’t natively supported in Eloquent. Create a custom query scope (e.g., `JsonSearchScope`) using `whereRaw` with raw SQL. Example: `JSON_SEARCH(column, 'one', ?)`. For complex searches, consider a package like `spatie/laravel-query-builder` for more flexibility.
- What Laravel versions support `becklyn/rad-bundle` adaptations, and are there PHP version conflicts?
- Laravel 8+ (PHP 8.0+) is recommended due to Symfony v8+ dependencies. Test for conflicts with `illuminate/support` or `symfony/bridge` by checking Composer’s `conflict` section. Avoid packages requiring Symfony ^5.4. Use `composer why-not` to diagnose version mismatches before integration.
- How do I handle the `DeferredRoute`, `DeferredTranslation`, and `DeferredForm` components in Laravel?
- These are Symfony-specific and require significant rewrites. For routes, use Laravel’s `Route::get()` or `RouteServiceProvider`. Translations can leverage Laravel’s `trans()` helper or `laravel-translation-manager`. Forms should use Laravel’s `FormRequest` validation instead of Symfony’s deferred validation. Plan for custom implementations if these features are critical.
- Is the `mojave` frontend library compatible with Laravel, or do I need a replacement?
- `mojave` is TypeScript-based and can work with Laravel if you adapt the `AjaxResponse` interface. Use a Laravel frontend package (e.g., `laravel-vue-frontend`) to bridge responses. Alternatively, write a custom TypeScript client that matches Laravel’s default JSON structure. Test thoroughly to avoid frontend logic breaks.
- What’s the best way to test Laravel adaptations of `becklyn/rad-bundle` components?
- Unit test middleware/traits with PHPUnit’s `HttpTestCase` for AJAX responses. For form extensions, test Blade components with `blade.test` or mock Laravel’s `Form` facade. Use Pest or Laravel Dusk for frontend integration tests. Focus on edge cases like empty collections or invalid JSON search queries.
- Should I use `becklyn/rad-bundle` in production, or are there better Laravel-native alternatives?
- For AJAX protocols, Laravel’s built-in `Response::json()` or packages like `spatie/laravel-response` may suffice. For forms, `laravelcollective/html` or `livewire/tailwind` offer native solutions. Evaluate the bundle’s components individually—adopt only what saves development time (e.g., AJAX) and rewrite or replace the rest.
- How do I maintain compatibility if Symfony dependencies (e.g., `AjaxResponseBuilder`) are updated or deprecated?
- Monitor Symfony’s deprecations (e.g., `BundleExtension` in v7.13.3) and refactor Laravel wrappers proactively. Use Composer’s `platform-check` to test PHP/Symfony version constraints. For critical updates, fork the bundle or create a Laravel-specific fork. Document your adaptations to streamline future maintenance.
Weaver
How can I help you explore Laravel packages today?