Download the PHP package eyf/laravel-autoroute without Composer
On this page you can find all versions of the php package eyf/laravel-autoroute. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
FAQ
Example:
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 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.
Informations about the package laravel-autoroute
laravel-autoroute
Autoroute helps you register Laravel routes as YAML.
"La route? Là où on va, on a pas besoin... De route."
Install
Usage
Note: It will automatically look for files inside the Laravel routes/ folder.
Sample api.yaml
Or using the compact syntax:
Template parameters
Autoroute supports light parameters in YAML files. The format is %<parameter_name>%.
For instance let's say you need to work with a local API subdomain:
And in your local .env file:
And in your api.yaml file:
Default route names
If you don't provide an as option in your route definition:
Autoroute will generate a default route name based on the current namespace, controller and action names:
Custom default route name
If you're not happy with the default route name format, you can implement your own Eyf\Autoroute\RouteNamerInterface and bind it accordingly in your Laravel app service provider:
uses compact syntax
If you're not using any route options (as, etc...), you can use a "compact" syntax to specify your controllers:
Custom compact syntax
You can customize the shorthand syntax by implementing RouteNamerInterface::getUses(string $compact).
