Download the PHP package routing-interop/route without Composer
On this page you can find all versions of the php package routing-interop/route. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
FAQ
After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.
Example:
Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories.
In this case some credentials are needed to access such packages.
Please use the auth.json textarea to insert credentials, if a package is coming from a private repository.
You can look here for more information.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?
Informations about the package route
routing-interop/route
Installation
Usage
Thougts
-
Most routing libraries use the following route declaration format:
addRoute(
, , ) pathcan be a string, a regex, or a custom format. It usually contains all the variable parts or the path, the type constraints.- Each path part is a segment (typical URI language).
- Simple string segments are static, while others are dynamic.
- Other route constraints not contained in
path:- Host
- Scheme
- Port
- A dynamic segment can be optional and have a default value
- Using a common static prefix for a bunch of routes is very useful
- Declaring a group of routes with the same path but not the same method can be useful
- What to do when no route is matched? Wrong URI, wrong method, ...
It may be useful to add default workflow and responses. - Giving a name to routes seems deprecated. Wait... no, it isn't: how do we generate URIs without names!?
- Content negotiation is not is the scope of routing
- Parameter conversion (from
/post/{slug}tocontroller(BlogPost $post)) is out of scope.
All versions of route with dependencies
PHP Build Version
Package Version
Requires
php Version
>=7.4
The package routing-interop/route contains the following files
Loading the files please wait ....