Weave Code
Routing Auto Bundle Laravel Package
symfony-cmf/routing-auto-bundle
Symfony CMF Routing Auto Bundle automatically generates and manages routes for content using configurable rules, making it easier to build dynamic, SEO-friendly URLs in Symfony applications without manual route creation.
Adding automatic route generating on top of the symfony cmf routing
Frequently asked questions about Routing Auto Bundle
- What does symfony-cmf/routing-auto-bundle do?
- It is a Symfony CMF bundle that automatically generates and manages routes for content based on configurable rules. Instead of manually creating routes, you define rules that map content fields to URL patterns, producing dynamic and SEO-friendly URLs. It builds on top of the Symfony CMF routing layer.
- How do I install symfony-cmf/routing-auto-bundle?
- Install it with Composer using composer require symfony-cmf/routing-auto-bundle, then enable the bundle in your Symfony kernel and configure routing auto rules. For version 2.1.0, confirm your project runs PHP 7.1+ and Symfony 3.3+/4.x before requiring it. In a Laravel app, verify that the bundle's Symfony dependencies can coexist with your framework version.
- Is symfony-cmf/routing-auto-bundle compatible with Laravel?
- It is not a native Laravel package; it is a Symfony CMF bundle. Laravel applications can sometimes consume Symfony components, but a full bundle typically expects Symfony's kernel and bundle system. Treat Laravel adoption as an integration project: audit composer.json constraints and test service container and routing behavior. For pure Laravel route generation, consider Laravel-native alternatives.
- What PHP and Symfony versions does version 2.1.0 require?
- Release 2.1.0 requires PHP 7.1+ and adds Symfony 4 support while removing PHP 5.6/7.0 and Symfony 3.0 through 3.2. The exact supported matrix should be verified against the package's composer.json and CI configuration. It is described as fitting Symfony 3.3+/4.x, but confirm whether Symfony 3.3/3.4 remains supported.
- Does version 2.1.0 support Symfony 3.3/3.4 or only Symfony 4?
- The assessment notes Symfony 4 support was added and legacy Symfony 3.0 through 3.2 were removed, but it is unclear whether 2.1.0 exclusively requires Symfony 4 or still supports 3.3/3.4. Check composer.json and CI to confirm the supported range. If you are on Symfony 3.3/3.4, test before upgrading or pin to 2.0.x if needed.
- How do I configure automatic route generation rules?
- You define route auto rules in configuration that map content properties to route patterns. The bundle then generates and manages routes when content is created or updated. Exact YAML or PHP configuration depends on the bundle version and your content model. Consult the package documentation and test rules in a staging environment.
- Can I upgrade from 2.0.x to 2.1.0 safely?
- Treat it as a platform-alignment upgrade, not a drop-in minor bump, because 2.1.0 drops PHP 5.6/7.0 and Symfony 3.0 through 3.2. Inventory composer.lock, upgrade PHP and Symfony first if needed, then adopt 2.1.0 and run regression tests. If you cannot move platforms, pin to the latest 2.0.x and set a review date. Look for an upgrade guide or changelog; if absent, request one or inspect the diff.
- What are alternatives to RoutingAutoBundle for Laravel route generation?
- For Laravel-native projects, use Laravel's routing, route model binding, or packages like spatie/laravel-sluggable for SEO-friendly slugs. For Symfony CMF, RoutingAutoBundle is the CMF-specific option; alternatives include manual route configuration or custom route generators. Evaluate based on whether you need content-driven automatic route management.
- Is symfony-cmf/routing-auto-bundle actively maintained and tested in CI?
- The TPM assessment raises questions about the supported matrix, CI coverage of lowest and highest dependency combinations, and security support for 2.0.x. Check the repository's CI configuration, release notes, and issue activity before adopting. If CI coverage is unclear, add your own integration tests. For production, confirm a maintenance policy or plan a fork or backport contingency.
- How should I test automatic route generation before production?
- Test route auto-generation in staging with representative content and rule changes, verifying generated URLs, redirects, and collisions. Run the package's test suite and your application's integration tests on the lowest and highest supported PHP and Symfony combinations. For production, canary a subset of content and monitor routing errors and SEO redirects.
Weaver
How can I help you explore Laravel packages today?