Download the PHP package fahrradkrucken/yaae without Composer

Yet Another AppEngine

This peace of "code" is a simple start point for your codebase. Please, keep in mind 3 simple facts: it's not a framework, it was written in about 16 hours, most of it made while author was drunk. The good part is - it has no external dependencies.

Application Lifecycle

Quick Start

Basically it's just a Request-Response handler. See simple example in demo/demo.php.

Action Callbacks

You can use any callable parameter, or some kind of Laravel style ControllerClass@actionMethod.

Request & Response

Well, Request & Response objects are not interesting at all, and they're not like PSR best practices. But! But you can manipulate them as you want, so they could become more pretty with your code. We have 3 rules:

• Request Handler accepts 1 arg RequestInterface $request and SHOULD return RequestInterface $request. If you'll not return RequestInterface, everything will be fine anyway, so you can just do something inside your "Request Middleware" and return nothing;
• Action handler accepts 2 args RequestInterface $request, ResponseInterface $response and SHOULD return ResponseInterface $response;

• Response Handler accepts 1 arg ResponseInterface $response and SHOULD return ResponseInterface $response. We have here the same rules as for request handlers.

  Request handlers will be executed from external (global or group) level to internal (individual route) level. Response handlers will be executed in reverse order.

Configuration

Main Config

You can replace request method and path through:

• $engine->setRequestPath(string $requestPath), default is $_SERVER['REQUEST_URI'], without / at the end and without params after ?;
• $engine->setRequestMethod(string $requestMethod), default is $_SERVER['REQUEST_METHOD']

You can replace default classes:

• FahrradKrucken\YAAE\Http\Request through $engine->setRequest(RequestInterface $request);
• FahrradKrucken\YAAE\Http\Response through $engine->setResponse(ResponseInterface $response);
• FahrradKrucken\YAAE\Core\RouteHandler through $engine->setRouteHandler(RouteHandlerInterface $routeHandler).

Errors

You can replace error handlers:

• \Throwable errors handler through $engine->setErrorHandler(callable $errorHandler);
• \FahrradKrucken\YAAE\Http\Error errors handler through $engine->setErrorHandlerHttp(callable $errorHandler).

Note that \FahrradKrucken\YAAE\Http\Error has $request and $response props, it could be useful. For example, when you'll get 404 (Not Found) or 405 (Method not allowed) error from RouteHandler, you can understand this by $errorHttp->getCode().

Examples for API errors:

Templating

HTML

You can use any templating engine you want, just dont forget to put the result inside the $response->setData($templateHtmlString). If you prefer simple php-html templating, you can use default FahrradKrucken\YAAE\Core\TemplateHandler. Example:

JSON & other API

If you need to send responses in JSON format (for example), you can add response handler to single route or to the route group. Like this: