Weave Code
Templated Uri Router Laravel Package
ezsystems/templated-uri-router
A Symfony URL generator that outputs RFC 6570 templated URIs, letting you build links with placeholders like /demo{?page,sort*,filter*} from route parameters. It's a small, naive implementation that covers basic needs only.
Symfony2 RFC-6570 compatible router and URL Generator
Frequently asked questions about Templated Uri Router
- Is ezsystems/templated-uri-router a Laravel package?
- No. It is a Symfony2 URL generator extension that implements RFC 6570 URI template expansion, built against Symfony2 routing components such as a route collection and request context. It has no Laravel service provider, facade, or config, and it does not hook into Laravel's router or UrlGenerator contracts. Treat it as a Symfony2-era component, not a Laravel dependency.
- What does this package actually generate?
- It outputs RFC 6570 templated URIs, so instead of a fully resolved link you get something like /demo{?page,sort*,filter*}. You pass placeholders as route parameters and the generator leaves them in the output for a client to expand later. The README describes the implementation as extremely naive and incomplete, covering basic needs only.
- Can I install it in a Laravel app with Composer?
- Technically Composer will resolve it if version constraints line up, but that does not make it safe or useful in Laravel. The package is archived, has essentially no dependents, and targets Symfony2 components that are long end-of-life, so autoloading and dependency conflicts are plausible. Any adoption needs a compatibility spike against your current PHP and Laravel versions before a proof of concept.
- Which PHP and Laravel versions does it support?
- The provided context does not list current version constraints, and the Symfony2 coupling suggests they are old and unlikely to align with modern Laravel releases. Symfony2 is end-of-life, so PHP support is a real open question rather than a documented guarantee. Validate PHP constraints, PSR compliance, autoloading, and encoding behavior in a throwaway branch before trusting it.
- Is this package still maintained?
- No. The repository is archived, it has roughly one star and zero dependents, and there is no vendor support or active maintainer. If you adopt it, your team owns bug fixes, PHP upgrades, and RFC 6570 correctness. That is a high maintenance burden for a narrow URL-formatting feature.
- Does it replace Laravel's route() helper or named routes?
- It does not integrate with Laravel's named routes, route model binding, signed URLs, or the UrlGenerator contract. Using it alongside route() would create a parallel routing abstraction that new engineers have to learn separately. For ordinary application links, Laravel's built-in URL generation is the correct choice.
- When would RFC 6570 URI templates be useful in a Laravel API?
- The main legitimate use case is hypermedia or API contract design, where a server advertises a link template such as /search{?q,page,sort*} and lets clients supply parameters. If your API documentation needs that shape, you can produce it with a small Laravel-native generator or a maintained URI-template library rather than an abandoned Symfony2 component. Confirm the business need first, because standard route URLs often suffice.
- What are the safer alternatives for templated links in Laravel?
- Look at actively maintained RFC 6570 libraries in the wider PHP ecosystem, or write a thin Laravel-native helper that builds templates from your route definitions. A small in-house generator keeps you in control of encoding rules and removes the Symfony2 dependency entirely. Build-versus-buy evaluation should happen before any proof of concept with this package.
- What are the known failure modes with reserved characters and array parameters?
- Incorrect expansion of reserved characters, optional and exploded operators, and array values are the expected risks, especially since the author calls the implementation naive and incomplete. Silent URL divergence between what your server advertises and what clients expand is a realistic outcome. If you must use it, add explicit tests for each operator and encoding edge case your API relies on.
- Should I use it in production or just as a design reference?
- The assessment recommends against vendoring it into a Laravel application for production. A better path is to use it as a reference for API contract design, isolate any existing Symfony2 usage behind an interface, and plan replacement with a maintained solution. If it stays a candidate, gate it behind a proof of concept, dependency and security review, and an abstraction layer.
Weaver
How can I help you explore Laravel packages today?