Rollerworks RouteAutowiringBundle
The RollerworksRouteAutowiringBundle allows to import multiple route collections
using an autowiring system., (*1)
For example you have BundleA which defines some routes, to use them you
need to explicitly import them, but if you remove/disable the bundle the
application breaks because it can't find the resource files anymore., (*2)
When you automatically enable them you can't keep the prefix consistent.
And sometimes you rather don't want to enable all route collections., (*3)
How does it work?
In practice you define your routes as normal, but instead of importing them
from a file or service you load them using the autowiring system., (*4)
Requirements
You need at least PHP 7.2 and the Symfony FrameworkBundle., (*5)
Installation
Open a command console, enter your project directory and execute the
following command to download the latest stable version of this bundle:, (*6)
$ php composer.phar require rollerworks/route-autowiring-bundle
This command requires you to have Composer installed globally, as explained
in the installation chapter
of the Composer documentation., (*7)
Basic usage
There are two parts to this bundle, registering and loading., (*8)
Routing schema's are kept per "routing-slot", which are automatically
registered whenever you import a route collection., (*9)
Registering routes for loading
Say you have an AcmeShopBundle with the following route collections:, (*10)
# Resources/config/routing/frontend.yml
_products:
resource: "routing/frontend/products.yml"
prefix: /products
_cart:
resource: "routing/frontend/cart.yml"
prefix: /cart
# Resources/config/routing/backend.yml
_products:
resource: "routing/backend/products.yml"
prefix: /products
You can import them using the following snippet:, (*11)
use Rollerworks\Bundle\RouteAutowiringBundle\RouteImporter;
use Symfony\Component\DependencyInjection\ContainerBuilder;
use Symfony\Component\DependencyInjection\Extension\Extension;
class AcmeShopExtension extends Extension
{
// ...
public function load(array $configs, ContainerBuilder $container): void
{
// ...
$routeImporter = new RouteImporter($container);
$routeImporter->addObjectResource($this);
$routeImporter->import('@AcmeShopBundle/Resources/config/routing/frontend.yml', 'frontend');
$routeImporter->import('@AcmeShopBundle/Resources/config/routing/backend.yml', 'backend');
}
// ...
}
The @AcmeShopBundle/Resources/config/routing/frontend.yml resource will be imported (or registered)
in the 'frontend' routing-slot. And the @AcmeShopBundle/Resources/config/routing/backend.yml
resource will be imported in the 'backend' routing slot., (*12)
Note:, (*13)
Route resources follow the same logic as the Symfony routing system,
@AcmeShopBundle resolves the to full path of the AcmeShopBundle., (*14)
See also: Including External Routing Resources, (*15)
Tip: You can import multiple routing resources per slot :+1:, (*16)
$routeImporter->import('@AcmeShopBundle/Resources/config/routing/frontend.yml', 'frontend');
$routeImporter->import('@AcmeShopBundle/Resources/config/routing/extra.yml', 'frontend');
The import will try to guess the correct resource-type, but for special ones (like a service)
you need to provide the type in the third parameter:, (*17)
$routeImporter->import('@AcmeShopBundle/Resources/config/routing/frontend.yml', 'frontend', 'yaml');
Import multiple resources to the same slot? Provide a default (for the current instance):, (*18)
$routeImporter = new RouteImporter($container, 'frontend');
$routeImporter->import('@AcmeShopBundle/Resources/config/routing/frontend.yml'); // is imported in the frontend slot
$routeImporter->import('@AcmeShopBundle/Resources/config/routing/backend.yml', 'backend'); // is imported in the backend slot
Resource tracking
The routing system is not directly aware of any related classes when registering
your route imports (using the RouteImporter). Therefor removing a Bundle
or changing configuration may not directly reload your routing schema
(unless you use the cache:clear command)., (*19)
You need to register the Extension class and any other related class,
like your Bundle's Configuration class, if changing them may cause
a different routing import schema., (*20)
To register an object (like the Extension class, and its parent(s)) use:, (*21)
$routeImporter->addObjectResource($this);, (*22)
Or to register a class (and its parent(s)):, (*23)
$routeImporter->addObjectClass($this);, (*24)
To register any Symfony supported Resource (full path) use:, (*25)
$routeImporter->addResource(new FileResource('my-file-file-path.yml'));, (*26)
Note:, (*27)
Resources are only tracked when debugging is enabled., (*28)
Imported routes (->import(...)) are automatically tracked by the routing system,
only classes related to the import registering should be registered for tracking., (*29)
Loading registered routes
Ones your routes are imported into there routing-slot's it's time
to load them into the application's routing schema., (*30)
Normally you would use something like this:, (*31)
# app/config/routing.yml
_frontend:
resource: "frontend.yml"
prefix: /
_backend:
resource: "frontend.yml"
prefix: /
# frontend.yml
_AcmeShop:
resource: "@AcmeShopBundle/Resources/config/routing/frontend.yml"
# backend.yml
_AcmeShop:
resource: "@AcmeShopBundle/Resources/config/routing/backend.yml"
But instead you load them using the autowiring loader:, (*32)
# app/config/routing.yml
_frontend:
resource: "frontend"
type: rollerworks_autowiring
prefix: /
_backend:
resource: "backend"
type: rollerworks_autowiring
prefix: backend/
That's it! All the routes that were imported in the 'frontend' and 'backend' slots
are now loaded into the applications routing schema., (*33)
But wait, what if there are no routes imported for the slot?, (*34)
Then nothing happens, this bundle is designed to make configuration easy.
When there are no routes imported for the slot it simple returns an empty Collection,
which in practice is never used., (*35)
Third-party import example
As the Symfony routing system allows to load any route resource from a routing file
you can actually load a routing-slot from within from another routing-slot., (*36)
Say you want to allow others to "extend" your bundle's routing schema:, (*37)
First import the main parts in the application's routing file:, (*38)
# app/config/routing.yml
_frontend:
resource: "frontend"
type: rollerworks_autowiring
prefix: /
_backend:
resource: "frontend"
type: rollerworks_autowiring
prefix: backend/
In AcmeShopBundle define the following routes,
and import them (extension snippet omitted)., (*39)
# Resources/config/routing/frontend.yml
_products:
resource: "routing/frontend/products.yml"
prefix: /products
_cart:
resource: "routing/frontend/cart.yml"
prefix: /cart
# Resources/config/routing/frontend.yml
_products:
resource: "routing/backend/products.yml"
prefix: /products
# Load other routing schema's from the routing-slot
_imports:
resource: "acme_shop.frontend"
type: rollerworks_autowiring
Others can now easily import there routing schema(s) into the
acme_shop.frontend routing-slot., (*40)
Versioning
For transparency and insight into the release cycle, and for striving
to maintain backward compatibility, this package is maintained under
the Semantic Versioning guidelines as much as possible., (*41)
Releases will be numbered with the following format:, (*42)
<major>.<minor>.<patch>, (*43)
And constructed with the following guidelines:, (*44)
- Breaking backward compatibility bumps the major (and resets the minor and patch)
- New additions without breaking backward compatibility bumps the minor (and resets the patch)
- Bug fixes and misc changes bumps the patch
For more information on SemVer, please visit http://semver.org/., (*45)
License
The package is provided under the MIT license., (*46)
Wallogit.com
