Weave Code
Templated Uri Bundle Laravel Package
ezsystems/templated-uri-bundle
Symfony bundle for the Hautelook TemplatedUriRouter library, adding an RFC-6570-compliant router and URL generator. It exposes the hautelook.router.template service so you can generate templated links with expressions such as {page} and {&sort*}. Install via Composer and register the bundle in y...
Expose the hautelook/TemplatedUriRouter in a symfony application
Frequently asked questions about Templated Uri Bundle
- Can I install ezsystems/templated-uri-bundle in a Laravel application?
- No. This is a Symfony bundle that registers HautelookTemplatedUriBundle in the Symfony kernel and exposes the hautelook.router.template container service, and Laravel neither consumes Symfony bundles nor has that service ID. Installing it in a Laravel app gives you no usable integration point. Treat it as a reference implementation only, and use a standalone RFC-6570 library behind your own Laravel service provider if you actually need templated URLs.
- How do I install and register this bundle?
- Run composer require hautelook/templated-uri-bundle and then add new HautelookTemplatedUriBundle() to the registerBundles() method in your Symfony AppKernel. If you use Symfony Flex it is registered automatically in bundles.php. Note that the Composer name shown for this repository (ezsystems/templated-uri-bundle) differs from the install command in the README, so confirm which canonical package you are actually pulling before you commit to it.
- What is the difference between ezsystems/templated-uri-bundle and hautelook/templated-uri-bundle?
- The repository is published under ezsystems/templated-uri-bundle but its README, badges, namespace, and install instructions all describe the Hautelook bundle, which suggests a rename or fork of the upstream package. The metadata inconsistency raises provenance and canonical-package questions that matter for audits and security review. Check whether the code is identical to upstream before relying on either name in a composer.json.
- Is there a maintained Laravel-friendly alternative for RFC-6570 URI templates?
- Yes. Guzzle's uri-template package, league/uri, and rize/uri-template all implement RFC-6570 expansion and are installable as plain Composer libraries with no Symfony coupling. In Laravel, bind an application-owned interface such as TemplatedUriGenerator to an adapter around the library in a service provider. That keeps the dependency swappable and isolated from Laravel's native UrlGenerator.
- Does this package support PHP 8.x and current Laravel versions?
- There is no evidence of PHP 8.x support or ongoing maintenance; the repository is archived with no dependents and only README and CHANGELOG as maturity signals. Its Symfony-era Composer constraints are likely to conflict with current Laravel and framework dependencies. Run a Composer dependency audit against your target PHP and Laravel versions before any design work, and do not force installation with --ignore-platform-reqs.
- What does the hautelook.router.template service actually generate?
- It generates RFC-6570 compliant URI templates rather than fully resolved URLs. Calling generate() with expressions in the parameter values, such as page set to {page} and sort set to an array containing {sort}, produces output like /demo?{&page}{&sort*}{&filter*}. Your client is then responsible for expanding those variables, which is useful for hypermedia and API link advertisement but not a drop-in replacement for normal route generation.
- Can I use the underlying TemplatedUriRouter library standalone in Laravel?
- Conceptually yes, since the reusable asset is the RFC-6570 expansion logic rather than the bundle wrapper. In practice the underlying library is also stale, so verify it installs cleanly on your PHP version first. If it does not, port the small expansion routine or delegate to a maintained library inside an application-owned class.
- How should I test URI template expansion in a Laravel integration?
- Write contract tests against your own interface, not the third-party code, covering expansion of required and optional variables, list and associative operators, URL encoding of reserved characters, missing variable handling, and deterministic output for caching. These tests are what make it safe to swap the underlying implementation later. Include at least one end-to-end test through the endpoint that emits templated links.
- Is it safe to build URI templates from untrusted input?
- Be careful. RFC-6570 expansion performs percent-encoding of substituted values, but the template expressions themselves must never be assembled from user input, and variable names should be validated against an allowlist. The bundle adds no validation layer of its own and only registers the router service. Treat placeholder validation and encoding as a real security review surface anywhere templated links appear in API or hypermedia output.
- Is the package actively maintained, and what happens if it is abandoned?
- It is not maintained: the repository is archived, has a single star and zero dependents, and shows no community or release activity. The MIT license permits forking, but a fork means you own that code forever. The pragmatic path is to confirm the business need for RFC-6570 templates, prototype with a maintained library behind an application-owned interface, and roll out behind a feature flag so you can replace it cleanly.
Weaver
How can I help you explore Laravel packages today?