gac/routing
Composer 安装命令:
composer require gac/routing
包简介
Custom routing library especially useful for fast API development
关键字:
README 文档
README
This library allows you to create static or dynamic routes. This library was inspired by PHP Slim framework
Install via composer
composer require gac/routing
Manual install
Download the latest release from the Releases page.
Don't forget to add these include_once statements to your php files:
include_once "./Exceptions/CallbackNotFound.php"; include_once "./Exceptions/RouteNotFoundException.php"; include_once "./Request.php"; include_once "./Routes.php";
Post install
To use this library properly you will need to create a .htaccess file at the root of the project.
Example of the .htaccess file would look like this:
RewriteEngine On RewriteBase / RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule ^(.+)$ index.php [QSA,L]
Note
If you've named your main file differently, replace index.php in the .htaccess file with whatever your main
application file is.
Quick start
Sample code to allow you to quickly start with your development.
use Gac\Routing\Exceptions\CallbackNotFound; use Gac\Routing\Exceptions\RouteNotFoundException; use Gac\Routing\Request; use Gac\Routing\Response; use Gac\Routing\Routes; include_once "vendor/autoload.php"; # IF YOU'RE USING composer $routes = new Routes(); try { $routes->add('/', function (Request $request) { // Old way of doing it, still supported until v4 $request ->status(200, "OK") ->send(["message" => "Welcome"]); // New way of doing it Response:: withHeader("Content-Type", "application/json"):: withStatus(200, 'OK'):: withBody([ "message" => "Welcome" ]):: send(); }); $routes->route('/', function (Request $request) { // Old way of doing it, still supported until v4 $request ->status(200, "OK") ->send(["message" => "Welcome"]); // New way of doing it Response:: withHeader("Content-Type", "application/json"):: withStatus(200, 'OK'):: withBody([ "message" => "Welcome" ]):: send(); }, [Routes::POST])->save(); $routes->route(); } catch (RouteNotFoundException $ex) { // Old way of doing it, still supported until v4 $routes->request->status(404, "Route not found")->send(["error" => ["message" => $ex->getMessage()]]); // New way of doing it Response::withStatus(404, 'Route not found')::send(["error" => [ "message" => $ex->getMessage() ]]); } catch (CallbackNotFound $ex) { // Old way of doing it, still supported until v4 $routes->request->status(404, "Callback not found")->send(["error" => ["message" => $ex->getMessage()]]); // New way of doing it Response::withStatus(404, 'Callback not found')::send(["error" => [ "message" => $ex->getMessage() ]]); } catch (Exception $ex) { $code = $ex->getCode() ?? 500; // Old way of doing it, still supported until v4 $routes->request->status($code)->send(["error" => ["message" => $ex->getMessage()]]); // New way of doing it Response::withStatus($code)::send(["error" => [ "message" => $ex->getMessage() ]]); }
Examples
Dynamic routes example
$routes->add('/test/{int:userID}-{username}/{float:amount}/{bool:valid}', function ( Request $request, int $userID, string $username, float $amount, bool $valid ) { echo 'Dynamic route content here'; });
Chained routes
When using chained methods either use ->save() or ->add() as the last method to indicate the end of a chain
NOTE
->save(true|false)method can still be chained onto if needed- Passing
false(the default value istrue) to the->save()method will preserve all the previous prefixes and middlewares in that chain
- Passing
->add()CAN NOT be chained onto and should be the last call in chain
$routes ->prefix('/user') // all the routes added will have the /user prefix ->middleware([ 'verify_token' ]) // all the routes added will have the verify_token middleware applied ->route('/', [ HomeController::class, 'getUsers' ], Routes::GET) ->route('/', [ HomeController::class, 'addUser' ], Routes::POST) ->route('/', [ HomeController::class, 'updateUser' ], Routes::PATCH) ->route('/', [ HomeController::class, 'replaceUser' ], Routes::PUT) ->add('/test', [ HomeController::class, 'deleteUser' ], Routes::DELETE);
Chained routes with save at the end
$routes ->prefix("/test") ->middleware(['decode_token']) ->route("/t0", function(Request $request){}) ->get("/t1", function (){}) ->post("/t2", function (){}) ->put("/t3", function (){}) ->patch("/t4", function (){}) ->delete("/t5", function (){}) ->save();
Chained routes with multiple chains in one call
$routes ->prefix("/test") ->middleware([ 'decode_token' ]) ->get("/t1", function () { }) // route would be: /test/t1 ->get("/t2", function () { }) // route would be: /test/t2 ->get("/t3", function () { }) // route would be: /test/t3 ->save(false) // by passing the false argument here, we keep all the previous shared data from the chain (previous prefix(es) and middlewares) ->prefix("/test2") ->middleware([ "verify_token" ]) ->get("/t4", function () { }) // route would be: /test/test2/t4 ->get("/t5", function () { }) // route would be: /test/test2/t5 ->get("/t6", function () { }) // route would be: /test/test2/t6 ->save() // by not passing the false argument here, we are removing all shared data from the previous chains (previous prefix(es) and middlewares) ->prefix("/test3") ->middleware([ "verify_token" ]) ->get("/t7", function () { }) // route would be: /test3/t7 ->get("/t8", function () { }) // route would be: /test3/t8 ->get("/t9", function () { }) // route would be: /test3/t9 ->add(); //using save or add at the end makes the chaining stop and allows for other independent routes to be added
Passing arguments to middleware methods
When working with middlewares you can also pass them arguments if you need to
use Gac\Routing\Response; $routes ->middleware([ 'test_middleware', 'has_roles' => 'admin,user', [ Middleware::class, 'test_method' ], [ Middleware::class, 'has_role', 'Admin', 'Moderator', [ 'User', 'Bot' ] ], ]) ->add('/test', function (Request $request) { // Old way of doing it, still supported until v4 $request->send([ 'msg' => 'testing' ]); //New way of doing it Response::send([ "msg" => "testing" ]); });
Every middleware function can also accept an argument of type Gac\Routing\Request at any position as long as it has
the proper type specified.
Optional parameters
$routes->add( '/demo/{id?}', function($id = 'defaultValue'){ echo "ID: . $id"; }, Routes::GET );
When calling this endpoint with /demo it will output ID: defaultValue and with /demo/123 it will output ID: 123
Dependency injection on route classes
When using classes to handle your route callback, and those classes have some dependencies that need to be injected through a constructor, you can specify them as an array of arguments to be injected or let the library try to auto-inject classes.
$routes->add( '/demo', [ HomeController::class, 'dependency_injection_test', [ new InjectedClass() ] ], Routes::GET );
You can also use named arguments or mix and match them
$routes->add( '/demo', [ HomeController::class, 'dependency_injection_test', [ "injected_var" => new InjectedClass(), new Middleware ] ], Routes::GET );
Letting the library auto-inject classes into the constructor
$routes->add( '/demo', [ InjectController::class ], Routes::GET );
NOTE
The library will always try to auto-inject classes (will skip ones with null as default value) if non are provided, and you're using a class for callbacks.
Use __invoke instead for single method classes
$routes->add( '/invoke', [ HomeController::class ], Routes::GET );
You can also use __invoke with dependency injection as well:
$routes->add( '/invoke', [ HomeController::class, [ new InjectedClass() ] ], Routes::GET );
For more examples look in the sample folder index.php file
Documentation
Source code documentation can be found at PHP Routing documentation page
Features
- Static routes
- Dynamic routes
- Dynamic routes with optional parameters
- Middlewares
- Pass arguments to middlewares
- Route prefixes
- Method chaining
- Dependency injection on classes
- Manual injection
- Auto-injection
gac/routing 适用场景与选型建议
gac/routing 是一款 基于 PHP 开发的 Composer 扩展包,目前已累计 1.39k 次下载、GitHub Stars 达 8, 最近一次更新时间为 2020 年 08 月 16 日, 在 PHP 生态内属于活跃度较高的组件。
它主要适用于以下技术方向: 「route」 「routing」 「api」 「middleware」 「libray」 等业务场景。在实际项目中,围绕这些方向常见需要落地的问题包括:接口对接、性能调优、并发安全、与既有框架(Laravel / ThinkPHP / Yii / Webman 等)的兼容适配,以及生产环境的日志埋点与稳定性保障。
我们在过去多个企业项目中使用过 gac/routing 或与其功能相近的方案,如果你在选型或落地过程中遇到问题,例如 版本兼容、二次改造、私有化封装、与内部系统对接、生产 BUG 排查,欢迎联系我们协助评估。
基于 gac/routing 在你已有业务上做功能扩展、字段裁剪、UI 适配、与内部账号 / 权限 / 日志系统的深度对接。
线上偶发问题、内存泄漏、慢查询、并发异常等排查修复;针对高流量场景做缓存、队列、索引层面的调优。
承接完整的项目从需求 → 设计 → 开发 → 上线 → 长期运维;也可按月提供技术保姆服务。
与 gac/routing 相关的其它包
同方向 / 同关键字的高下载量 PHP Composer 包推荐,方便对比选型:
Provide a way to secure accesses to all routes of an symfony application.
Write down your routing mapping at one place
A Laravel-like router for the WordPress Rewrite API
A PSR-7 compatible library for making CRUD API endpoints
Flight routing is a simple, fast PHP router that is easy to get integrated with other routers.
A Laravel helper to detect if the current route/path is active.
统计信息
- 总下载量: 1.39k
- 月度下载量: 0
- 日度下载量: 0
- 收藏数: 8
- 点击次数: 11
- 依赖项目数: 0
- 推荐数: 0
其他信息
- 授权协议: GPL-3.0-only
- 更新时间: 2020-08-16