Skip to content
This repository has been archived by the owner on Jun 3, 2018. It is now read-only.

Latest commit

 

History

History
269 lines (193 loc) · 8.29 KB

README.md

File metadata and controls

269 lines (193 loc) · 8.29 KB
Raw

Table of Contents

DeFlip

DeFlip is a simple starter project to make a perfect landing website, support API calls within application. It's super fast (see benchmark.md) and has minimal dependency. Below is the current features:

  • PSR-7 HTTP Interface
  • Robust routing
  • Clean template engine
  • API calls using Guzzle wrapped inside Zttp
  • Auto resolve static template as web route

Quickstart

Running:

composer install

php -S localhost:8000 -t public/

Development:


TBD

Routing

Basic Routing

You will define all of the routes for your application in the routes.php file. The most basic routes simply accept a URI and a Closure:

$router->get('foo', function () {
    return 'Hello World';
});

$router->post('foo', function () {
    //
});

$router->view('/', 'home');

Available Router Methods

The router allows you to register routes that respond to any HTTP verb:

$router->get($uri, $callback);
$router->post($uri, $callback);
$router->put($uri, $callback);
$router->patch($uri, $callback);
$router->delete($uri, $callback);
$router->options($uri, $callback);
$router->view($uri, $view);

Route Parameters

Required Parameters

Of course, sometimes you will need to capture segments of the URI within your route. For example, you may need to capture a user's ID from the URL. You may do so by defining route parameters:

$router->get('user/{id}', function ($id) {
    return 'User '.$id;
});

You may define as many route parameters as required by your route:

$router->get('posts/{postId}/comments/{commentId}', function ($postId, $commentId) {
    //
});

Route parameters are always encased within "curly" braces. The parameters will be passed into your route's Closure when the route is executed.

Note: Route parameters cannot contain the - character. Use an underscore (_) instead.

Optional Parameters

You may define optional route parameters by enclosing part of the route URI definition in [...]. So, for example, /foo[bar] will match both /foo and /foobar. Optional parameters are only supported in a trailing position of the URI. In other words, you may not place an optional parameter in the middle of a route definition:

$router->get('user[/{name}]', function ($name = null) {
    return $name;
});

Regular Expression Constraints

You may constrain the format of your route parameters by defining a regular expression in your route definition:

$router->get('user/{name:[A-Za-z]+}', function ($name) {
    //
});

Named Routes

Named routes allow the convenient generation of URLs or redirects for specific routes. You may specify a name for a route using the as array key when defining the route:

$router->get('profile', ['as' => 'profile', function () {
    //
}]);

You may also specify route names for controller actions:

$router->get('profile', [
    'as' => 'profile', 'uses' => 'UserController@showProfile'
]);

Generating URLs To Named Routes

Once you have assigned a name to a given route, you may use the route's name when generating URLs or redirects via the global route function:

// Generating URLs...
$url = route('profile');

// Generating Redirects...
return redirect()->route('profile');

If the named route defines parameters, you may pass the parameters as the second argument to the route function. The given parameters will automatically be inserted into the URL in their correct positions:

$router->get('user/{id}/profile', ['as' => 'profile', function ($id) {
    //
}]);

$url = route('profile', ['id' => 1]);

Route Groups

Route groups allow you to share route attributes, such as middleware or namespaces, across a large number of routes without needing to define those attributes on each individual route. Shared attributes are specified in an array format as the first parameter to the $router->group method.

To learn more about route groups, we'll walk through several common use-cases for the feature.

Middleware

To assign middleware to all routes within a group, you may use the middleware key in the group attribute array. Middleware will be executed in the order you define this array:

$router->group(['middleware' => 'auth'], function ($router) use ($app) {
    $router->get('/', function ()    {
        // Uses Auth Middleware
    });

    $router->get('user/profile', function () {
        // Uses Auth Middleware
    });
});

Namespaces

Another common use-case for route groups is assigning the same PHP namespace to a group of controllers. You may use the namespace parameter in your group attribute array to specify the namespace for all controllers within the group:

$router->group(['namespace' => 'Admin'], function($router) use ($app)
{
    // Using The "App\Http\Controllers\Admin" Namespace...

    $router->group(['namespace' => 'User'], function() use ($app) {
        // Using The "App\Http\Controllers\Admin\User" Namespace...
    });
});

Route Prefixes

The prefix group attribute may be used to prefix each route in the group with a given URI. For example, you may want to prefix all route URIs within the group with admin:

$router->group(['prefix' => 'admin'], function ($router) use ($app) {
    $router->get('users', function ()    {
        // Matches The "/admin/users" URL
    });
});

You may also use the prefix parameter to specify common parameters for your grouped routes:

$router->group(['prefix' => 'accounts/{accountId}'], function ($router) use ($app) {
    $router->get('detail', function ($accountId)    {
        // Matches The "/accounts/{accountId}/detail" URL
    });
});

Auto Resolve Routing

DeFlip works with static routing out of the box. If you don't register your application route within routes.php file, the application will try to find appropriate view to be rendered. For example:

Given Route View to be Rendered
/ /views/index.php
/about /views/about.php
/foo/bar /views/foo/bar.php

You can serve a static file within dynamic route, for example, if client want to access /blog/good-developer-101 page, DeFlip will try to find /views/blog/good-developer-101.php file. If this file does not exists, then it will try to find /views/blog/_id.php file. If this file exists, you can access the route parameter via $id variable.

<?php echo $this->e($id) ?> <!-- output is 'good-developer-101' -->

DeFlip also handle any exception out of the box, simply create a /views/500.php file, any exception (EXCEPT HttpException) will be rendered into this view. If the exception is an instance of HttpException, DeFlip will try to find /views/{HTTP_STATUS_CODE}.php file. For instance, if you want to handle a NotFoundHttpException simply create /views/404.php file and if you want to handle MethodNotAllowedHttpException simply create /views/405.php file.

Template

DeFlip uses Plates as it's default template engine. For more information about Plates, see here.