rework with syntax highlighting

Reworked the README to include syntax highlighting for sanity while reading, as well as a few posed changes for `uniformity`.
pull/26/head
Zachary Queal 12 years ago
parent 4cf069a552
commit 03b4dfe825

@ -1,21 +1,22 @@
# What is Flight? # What is Flight?
Flight is a fast, simple, extensible framework for PHP. Flight is a fast, simple, extensible framework for PHP. Flight enables you to quickly and easily build RESTful web applications.
Flight enables you to quickly and easily build RESTful web applications.
require 'flight/Flight.php'; ```php
require 'flight/Flight.php';
Flight::route('/', function(){ Flight::route('/', function(){
echo 'hello world!'; echo 'hello world!';
}); });
Flight::start(); Flight::start();
```
[Learn more](http://flightphp.com/learn) [Learn more](http://flightphp.com/learn)
# Requirements # Requirements
Flight requires PHP 5.3 or greater. Flight requires `PHP 5.3` or greater.
# License # License
@ -27,83 +28,101 @@ Flight is released under the [MIT](http://www.opensource.org/licenses/mit-licens
2\. Configure your webserver. 2\. Configure your webserver.
For *Apache*, edit your .htaccess file with the following: For *Apache*, edit your `.htaccess` file with the following:
RewriteEngine On ```
RewriteCond %{REQUEST_FILENAME} !-f RewriteEngine On
RewriteCond %{REQUEST_FILENAME} !-d RewriteCond %{REQUEST_FILENAME} !-f
RewriteRule ^(.*)$ index.php [QSA,L] RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^(.*)$ index.php [QSA,L]
```
For *Nginx*, add the following to your server declaration: For *Nginx*, add the following to your server declaration:
server { ```
location / { server {
try_files $uri $uri/ /index.php; location / {
} try_files $uri $uri/ /index.php;
} }
}
3\. Create your index.php file. ```
3\. Create your `index.php` file.
First include the framework. First include the framework.
require 'flight/Flight.php'; ```php
require 'flight/Flight.php';
```
Then define a route and assign a function to handle the request. Then define a route and assign a function to handle the request.
Flight::route('/', function(){ ```php
echo 'hello world!'; Flight::route('/', function(){
}); echo 'hello world!';
});
```
Finally, start the framework. Finally, start the framework.
Flight::start(); ```php
Flight::start();
```
# Routing # Routing
Routing in Flight is done by matching a URL pattern with a callback function. Routing in Flight is done by matching a URL pattern with a callback function.
Flight::route('/', function(){ ```php
echo 'hello world!'; Flight::route('/', function(){
}); echo 'hello world!';
});
```
The callback can be any object that is callable. So you can use a regular function: The callback can be any object that is callable. So you can use a regular function:
function hello(){ ```php
echo 'hello world!'; function hello(){
} echo 'hello world!';
}
Flight::route('/', 'hello'); Flight::route('/', 'hello');
```
Or a class method: Or a class method:
class Greeting { ```php
public static function hello() { class Greeting {
echo 'hello world!'; public static function hello() {
} echo 'hello world!';
} }
}
Flight::route('/', array('Greeting','hello')); Flight::route('/', array('Greeting','hello'));
```
Routes are matched in the order they are defined. The first route to match a request will be invoked. Routes are matched in the order they are defined. The first route to match a request will be invoked.
## Method Routing ## Method Routing
By default, route patterns are matched against all request methods. You can respond to specific By default, route patterns are matched against all request methods. You can respond to specific methods by placing an identifier before the URL.
methods by placing an identifier before the URL.
Flight::route('GET /', function(){ ```php
echo 'I received a GET request.'; Flight::route('GET /', function(){
}); echo 'I received a GET request.';
});
Flight::route('POST /', function(){ Flight::route('POST /', function(){
echo 'I received a POST request.'; echo 'I received a POST request.';
}); });
```
You can also map multiple methods to a single callback by using a `|` delimiter: You can also map multiple methods to a single callback by using a `|` delimiter:
Flight::route('GET|POST /', function(){ ```php
echo 'I received either a GET or a POST request.'; Flight::route('GET|POST /', function(){
}); echo 'I received either a GET or a POST request.';
});
```
Method specific routes have precedence over global routes. Method specific routes have precedence over global routes.
@ -111,36 +130,44 @@ Method specific routes have precedence over global routes.
You can use regular expressions in your routes: You can use regular expressions in your routes:
Flight::route('/user/[0-9]+', function(){ ```php
// This will match /user/1234 Flight::route('/user/[0-9]+', function(){
}); // This will match /user/1234
});
```
## Named Parameters ## Named Parameters
You can specify named parameters in your routes which will be passed along to your callback function. You can specify named parameters in your routes which will be passed along to your callback function.
Flight::route('/@name/@id', function($name, $id){ ```php
echo "hello, $name ($id)!"; Flight::route('/@name/@id', function($name, $id){
}); echo "hello, $name ($id)!";
});
```
You can also include regular expressions with your named parameters by using the `:` delimiter: You can also include regular expressions with your named parameters by using the `:` delimiter:
Flight::route('/@name/@id:[0-9]{3}', function($name, $id){ ```php
// This will match /bob/123 Flight::route('/@name/@id:[0-9]{3}', function($name, $id){
// But will not match /bob/12345 // This will match /bob/123
}); // But will not match /bob/12345
});
```
## Optional Parameters ## Optional Parameters
You can specify named parameters that are optional for matching by wrapping segments in parentheses. You can specify named parameters that are optional for matching by wrapping segments in parentheses.
Flight::route('/blog(/@year(/@month(/@day)))', function($year, $month, $day){ ```php
// This will match the following URLS: Flight::route('/blog(/@year(/@month(/@day)))', function($year, $month, $day){
// /blog/2012/12/10 // This will match the following URLS:
// /blog/2012/12 // /blog/2012/12/10
// /blog/2012 // /blog/2012/12
// /blog // /blog/2012
}); // /blog
});
```
Any optional parameters that are not matched will be passed in as NULL. Any optional parameters that are not matched will be passed in as NULL.
@ -148,15 +175,19 @@ Any optional parameters that are not matched will be passed in as NULL.
Matching is only done on individual URL segments. If you want to match multiple segments you can use the `*` wildcard. Matching is only done on individual URL segments. If you want to match multiple segments you can use the `*` wildcard.
Flight::route('/blog/*', function(){ ```php
// This will match /blog/2000/02/01 Flight::route('/blog/*', function(){
}); // This will match /blog/2000/02/01
});
```
To route all requests to a single callback, you can do: To route all requests to a single callback, you can do:
Flight::route('*', function(){ ```php
// Do something Flight::route('*', function(){
}); // Do something
});
```
# Extending # Extending
@ -166,128 +197,146 @@ Flight is designed to be an extensible framework. The framework comes with a set
To map your own custom method, you use the `map` function: To map your own custom method, you use the `map` function:
// Map your method ```php
Flight::map('hello', function($name){ // Map your method
echo "hello $name!"; Flight::map('hello', function($name){
}); echo "hello $name!";
});
// Call your custom method // Call your custom method
Flight::hello('Bob'); Flight::hello('Bob');
```
## Registering Classes ## Registering Classes
To register your own class, you use the `register` function: To register your own class, you use the `register` function:
// Register your class ```php
Flight::register('user', 'User'); // Register your class
Flight::register('user', 'User');
// Get an instance of your class // Get an instance of your class
$user = Flight::user(); $user = Flight::user();
```
The register method also allows you to pass along parameters to your class constructor. So when you load your custom class, it will come pre-initialized. You can define the constructor parameters by passing in an additional array. Here's an example of loading a database connection: The register method also allows you to pass along parameters to your class constructor. So when you load your custom class, it will come pre-initialized. You can define the constructor parameters by passing in an additional array. Here's an example of loading a database connection:
// Register class with constructor parameters ```php
Flight::register('db', 'Database', array('localhost','mydb','user','pass')); // Register class with constructor parameters
Flight::register('db', 'Database', array('localhost','mydb','user','pass'));
// Get an instance of your class // Get an instance of your class
// This will create an object with the defined parameters // This will create an object with the defined parameters
// //
// new Database('localhost', 'mydb', 'user', 'pass'); // new Database('localhost', 'mydb', 'user', 'pass');
// //
$db = Flight::db(); $db = Flight::db();
```
If you pass in an additional callback parameter, it will be executed immediately after class construction. This allows you to perform any set up procedures for your new object. The callback function takes one parameter, an instance of the new object. If you pass in an additional callback parameter, it will be executed immediately after class construction. This allows you to perform any set up procedures for your new object. The callback function takes one parameter, an instance of the new object.
// The callback will be passed the object that was constructed ```php
Flight::register('db', 'Database', array('localhost', 'mydb', 'user', 'pass'), function($db){ // The callback will be passed the object that was constructed
$db->connect(); Flight::register('db', 'Database', array('localhost', 'mydb', 'user', 'pass'), function($db){
}); $db->connect();
});
```
By default, every time you load your class you will get a shared instance. By default, every time you load your class you will get a shared instance.
To get a new instance of a class, simply pass in `false` as a parameter: To get a new instance of a class, simply pass in `false` as a parameter:
// Shared instance of Database class ```php
$shared = Flight::db(); // Shared instance of Database class
$shared = Flight::db();
// New instance of Database class // New instance of Database class
$new = Flight::db(false); $new = Flight::db(false);
```
Keep in mind that mapped methods have precedence over registered classes. If you declare both Keep in mind that mapped methods have precedence over registered classes. If you declare both using the same name, only the mapped method will be invoked.
using the same name, only the mapped method will be invoked.
# Overriding # Overriding
Flight allows you to override its default functionality to suit your own needs, without having to modify any code. Flight allows you to override its default functionality to suit your own needs, without having to modify any code.
For example, when Flight cannot match a URL to a route, it invokes the `notFound` method which sends a generic HTTP 404 response. For example, when Flight cannot match a URL to a route, it invokes the `notFound` method which sends a generic `HTTP 404` response.
You can override this behavior by using the `map` method: You can override this behavior by using the `map` method:
Flight::map('notFound', function(){ ```php
// Display custom 404 page Flight::map('notFound', function(){
include 'errors/404.html'; // Display custom 404 page
}); include 'errors/404.html';
});
```
Flight also allows you to replace core components of the framework. Flight also allows you to replace core components of the framework.
For example you can replace the default Router class with your own custom class: For example you can replace the default Router class with your own custom class:
// Register your custom class ```php
Flight::register('router', 'MyRouter'); // Register your custom class
Flight::register('router', 'MyRouter');
// When Flight loads the Router instance, it will load your class // When Flight loads the Router instance, it will load your class
$myrouter = Flight::router(); $myrouter = Flight::router();
```
Framework methods like `map` and `register` however cannot be overridden. You will get an error if you try to do so. Framework methods like `map` and `register` however cannot be overridden. You will get an error if you try to do so.
# Filtering # Filtering
Flight allows you to filter methods before and after they are called. There are no predefined hooks Flight allows you to filter methods before and after they are called. There are no predefined hooks you need to memorize. You can filter any of the default framework methods as well as any custom methods that you've mapped.
you need to memorize. You can filter any of the default framework methods as well as any custom methods that
you've mapped.
A filter function looks like this: A filter function looks like this:
function(&$params, &$output) { ```php
// Filter code function(&$params, &$output) {
} // Filter code
}
```
Using the passed in variables you can manipulate the input parameters and/or the output. Using the passed in variables you can manipulate the input parameters and/or the output.
You can have a filter run before a method by doing: You can have a filter run before a method by doing:
Flight::before('start', function(&$params, &$output){ ```php
// Do something Flight::before('start', function(&$params, &$output){
}); // Do something
});
```
You can have a filter run after a method by doing: You can have a filter run after a method by doing:
Flight::after('start', function(&$params, &$output){ ```php
// Do something Flight::after('start', function(&$params, &$output){
}); // Do something
});
```
You can add as many filters as you want to any method. They will be called in the order You can add as many filters as you want to any method. They will be called in the order that they are declared.
that they are declared.
Here's an example of the filtering process: Here's an example of the filtering process:
// Map a custom method ```php
Flight::map('hello', function($name){ // Map a custom method
return "Hello, $name!"; Flight::map('hello', function($name){
}); return "Hello, $name!";
});
// Add a before filter
Flight::before('hello', function(&$params, &$output){ // Add a before filter
// Manipulate the parameter Flight::before('hello', function(&$params, &$output){
$params[0] = 'Fred'; // Manipulate the parameter
}); $params[0] = 'Fred';
});
// Add an after filter
Flight::after('hello', function(&$params, &$output){
// Manipulate the output
$output .= " Have a nice day!";
}
// Invoke the custom method // Add an after filter
echo Flight::hello('Bob'); Flight::after('hello', function(&$params, &$output){
// Manipulate the output
$output .= " Have a nice day!";
}
// Invoke the custom method
echo Flight::hello('Bob');
```
This should display: This should display:
@ -295,62 +344,74 @@ This should display:
If you have defined multiple filters, you can break the chain by returning `false` in any of your filter functions: If you have defined multiple filters, you can break the chain by returning `false` in any of your filter functions:
Flight::before('start', function(&$params, &$output){ ```php
echo 'one'; Flight::before('start', function(&$params, &$output){
}); echo 'one';
});
Flight::before('start', function(&$params, &$output){ Flight::before('start', function(&$params, &$output){
echo 'two'; echo 'two';
// This will end the chain // This will end the chain
return false; return false;
}); });
// This will not get called // This will not get called
Flight::before('start', function(&$params, &$output){ Flight::before('start', function(&$params, &$output){
echo 'three'; echo 'three';
}); });
```
Note, core methods such as `map` and `register` cannot be filtered because they are called Note, core methods such as `map` and `register` cannot be filtered because they are called directly and not invoked dynamically.
directly and not invoked dynamically.
# Variables # Variables
Flight allows you to save variables so that they can be used anywhere in your application. Flight allows you to save variables so that they can be used anywhere in your application.
// Save your variable ```php
Flight::set('id', 123); // Save your variable
Flight::set('id', 123);
// Elsewhere in your application
$id = Flight::get('id');
// Elsewhere in your application
$id = Flight::get('id');
```
To see if a variable has been set you can do: To see if a variable has been set you can do:
if (Flight::has('id')) { ```php
// Do something if (Flight::has('id')) {
} // Do something
}
```
You can clear a variable by doing: You can clear a variable by doing:
// Clears the id variable ```php
Flight::clear('id'); // Clears the id variable
Flight::clear('id');
// Clears all variables // Clears all variables
Flight::clear(); Flight::clear();
```
Flight also uses variables for configuration purposes. Flight also uses variables for configuration purposes.
Flight::set('flight.log_errors', true); ```php
Flight::set('flight.log_errors', true);
```
# Views # Views
Flight provides some basic templating functionality by default. To display a view template call the `render` method with the name of the template file and optional template data: Flight provides some basic templating functionality by default. To display a view template call the `render` method with the name of the template file and optional template data:
Flight::render('hello.php', array('name' => 'Bob')); ```php
Flight::render('hello.php', array('name' => 'Bob'));
```
The template data you pass in is automatically injected into the template and can be reference like a local variable. Template files are simply PHP files. If the content of the `hello.php` template file is: The template data you pass in is automatically injected into the template and can be reference like a local variable. Template files are simply PHP files. If the content of the `hello.php` template file is:
Hello, '<?php echo $name; ?>'! ```php
Hello, '<?php echo $name; ?>'!
```
The output would be: The output would be:
@ -358,250 +419,275 @@ The output would be:
You can also manually set view variables by using the set method: You can also manually set view variables by using the set method:
Flight::view()->set('name', 'Bob'); ```php
Flight::view()->set('name', 'Bob');
```
The variable `name` is now available across all your views. So you can simply do: The variable `name` is now available across all your views. So you can simply do:
Flight::render('hello'); ```php
Flight::render('hello');
```
Note that when specifying the name of the template in the render method, you can leave out the .php extension. Note that when specifying the name of the template in the render method, you can leave out the `.php` extension.
By default Flight will look for a `views` directory for template files. You can set an alternate path for your templates by setting the following config: By default Flight will look for a `views` directory for template files. You can set an alternate path for your templates by setting the following config:
Flight::set('flight.views.path', '/path/to/views'); ```php
Flight::set('flight.views.path', '/path/to/views');
```
## Layouts ## Layouts
It is common for websites to have a single layout template file with interchanging content. To render content to be used in a layout, you can pass in an optional parameter to the `render` method. It is common for websites to have a single layout template file with interchanging content. To render content to be used in a layout, you can pass in an optional parameter to the `render` method.
Flight::render('header', array('heading' => 'Hello'), 'header_content'); ```php
Flight::render('body', array('message' => 'World'), 'body_content'); Flight::render('header', array('heading' => 'Hello'), 'header_content');
Flight::render('body', array('message' => 'World'), 'body_content');
```
Your view will then have saved variables called `header_content` and `body_content`. You can then render your layout by doing: Your view will then have saved variables called `header_content` and `body_content`. You can then render your layout by doing:
Flight::render('layout', array('title' => 'Home Page')); ```php
Flight::render('layout', array('title' => 'Home Page'));
```
If the template files looks like this: If the template files looks like this:
header.php: `header.php`:
<h1><?php echo $heading; ?></h1> ```php
<h1><?php echo $heading; ?></h1>
```
body.php: `body.php`:
<div><?php echo $body; ?></div> ```php
<div><?php echo $body; ?></div>
```
layout.php: `layout.php`:
<html> ```php
<head> <html>
<title><?php echo $title; ?></title> <head>
</head> <title><?php echo $title; ?></title>
<body> </head>
<?php echo $header_content; ?> <body>
<?php echo $body_content; ?> <?php echo $header_content; ?>
</body> <?php echo $body_content; ?>
</html> </body>
</html>
```
The output would be: The output would be:
```html
<html> <html>
<head> <head>
<title>Home Page</title> <title>Home Page</title>
</head> </head>
<body> <body>
<h1>Hello</h1> <h1>Hello</h1>
<div>World</div> <div>World</div>
</body> </body>
</html> </html>
```
## Custom Views ## Custom Views
Flight allows you to swap out the default view engine simply by registering your own view class. Flight allows you to swap out the default view engine simply by registering your own view class. Here's how you would use the [Smarty](http://www.smarty.net/) template engine for your views:
Here's how you would use the [Smarty](http://www.smarty.net/) template engine for your views:
// Load Smarty library ```php
require './Smarty/libs/Smarty.class.php'; // Load Smarty library
require './Smarty/libs/Smarty.class.php';
// Register Smarty as the view class // Register Smarty as the view class
// Also pass a callback function to configure Smarty on load // Also pass a callback function to configure Smarty on load
Flight::register('view', 'Smarty', array(), function($smarty){ Flight::register('view', 'Smarty', array(), function($smarty){
$smarty->template_dir = './templates/'; $smarty->template_dir = './templates/';
$smarty->compile_dir = './templates_c/'; $smarty->compile_dir = './templates_c/';
$smarty->config_dir = './config/'; $smarty->config_dir = './config/';
$smarty->cache_dir = './cache/'; $smarty->cache_dir = './cache/';
}); });
// Assign template data // Assign template data
Flight::view()->assign('name', 'Bob'); Flight::view()->assign('name', 'Bob');
// Display the template // Display the template
Flight::view()->display('hello.tpl'); Flight::view()->display('hello.tpl');
```
For completeness, you should also override Flight's default render method: For completeness, you should also override Flight's default render method:
Flight::map('render', function($template, $data){ ```php
Flight::view()->assign($data); Flight::map('render', function($template, $data){
Flight::view()->display($template); Flight::view()->assign($data);
}); Flight::view()->display($template);
});
```
# Error Handling # Error Handling
## Errors and Exceptions ## Errors and Exceptions
All errors and exceptions are caught by Flight and passed to the `error` method. All errors and exceptions are caught by Flight and passed to the `error` method.
The default behavior is to send a generic HTTP `500 Internal Server Error` response with some error information. The default behavior is to send a generic `HTTP 500 Internal Server Error` response with some error information.
You can override this behavior for your own needs: You can override this behavior for your own needs:
Flight::map('error', function(){ ```php
// Handle error Flight::map('error', function(){
}); // Handle error
});
```
By default errors are not logged to the web server. You can enable this by changing the config: By default errors are not logged to the web server. You can enable this by changing the config:
Flight::set('flight.log_errors', true); ```php
Flight::set('flight.log_errors', true);
```
## Not Found ## Not Found
When a URL can't be found, Flight calls the `notFound` method. The default behavior is to When a URL can't be found, Flight calls the `notFound` method. The default behavior is to send an `HTTP 404 Not Found` response with a simple message.
send an HTTP `404 Not Found` response with a simple message. You can override this behavior for your own needs:
You can override this behavior for your own needs:
Flight::map('notFound', function(){ ```php
// Handle not found Flight::map('notFound', function(){
}); // Handle not found
});
```
# Redirects # Redirects
You can redirect the current request by using the `redirect` method and passing in a new URL: You can redirect the current request by using the `redirect` method and passing in a new URL:
Flight::redirect('/new/location'); ```php
Flight::redirect('/new/location');
```
# Requests # Requests
Flight encapsulates the HTTP request into a single object, which can be accessed by doing: Flight encapsulates the HTTP request into a single object, which can be accessed by doing:
$request = Flight::request(); ```php
$request = Flight::request();
```
The request object provides the following properties: The request object provides the following properties:
url - The URL being requested ```
base - The parent subdirectory of the URL url - The URL being requested
method - The request method (GET, POST, PUT, DELETE) base - The parent subdirectory of the URL
referrer - The referrer URL method - The request method (GET, POST, PUT, DELETE)
ip - IP address of the client referrer - The referrer URL
ajax - Whether the request is an AJAX request ip - IP address of the client
scheme - The server protocol (http, https) ajax - Whether the request is an AJAX request
user_agent - Browser information scheme - The server protocol (http, https)
body - Raw data from the request body user_agent - Browser information
type - The content type body - Raw data from the request body
length - The content length type - The content type
query - Query string parameters length - The content length
data - Post parameters query - Query string parameters
cookies - Cookie parameters data - Post parameters
files - Uploaded files cookies - Cookie parameters
files - Uploaded files
```
You can access the `query`, `data`, `cookies`, and `files` properties as arrays or objects. You can access the `query`, `data`, `cookies`, and `files` properties as arrays or objects.
So, to get a query string parameter, you can do: So, to get a query string parameter, you can do:
$id = Flight::request()->query['id']; ```php
$id = Flight::request()->query['id'];
```
Or you can do: Or you can do:
$id = Flight::request()->query->id; ```php
$id = Flight::request()->query->id;
```
# HTTP Caching # HTTP Caching
Flight provides built-in support for HTTP level caching. If the caching condition is met, Flight provides built-in support for HTTP level caching. If the caching condition is met, Flight will return an HTTP `304 Not Modified` response. The next time the client requests the same resource, they will be prompted to use their locally cached version.
Flight will return an HTTP `304 Not Modified` response. The next time the client requests the same resource,
they will be prompted to use their locally cached version.
## Last-Modified ## Last-Modified
You can use the `lastModified` method and pass in a UNIX timestamp to set the date and time a page was last modified. You can use the `lastModified` method and pass in a UNIX timestamp to set the date and time a page was last modified. The client will continue to use their cache until the last modified value is changed.
The client will continue to use their cache until the last modified value is changed.
Flight::route('/news', function(){ ```php
Flight::lastModified(1234567890); Flight::route('/news', function(){
echo 'This content will be cached.'; Flight::lastModified(1234567890);
}); echo 'This content will be cached.';
});
```
## ETag ## ETag
ETag caching is similar to Last-Modified, except you can specify any id you want for the resource: `ETag` caching is similar to `Last-Modified`, except you can specify any id you want for the resource:
Flight::route('/news', function(){ ```php
Flight::etag('my-unique-id'); Flight::route('/news', function(){
echo 'This content will be cached.'; Flight::etag('my-unique-id');
}); echo 'This content will be cached.';
});
```
Keep in mind that calling either `lastModified` or `etag` will both set and check the cache value. Keep in mind that calling either `lastModified` or `etag` will both set and check the cache value. If the cache value is the same between requests, Flight will immediately send an `HTTP 304` response and stop processing.
If the cache value is the same between requests, Flight will immediately send an HTTP 304 response and stop
processing.
# Stopping # Stopping
You can stop the framework at any point by calling the `halt` method: You can stop the framework at any point by calling the `halt` method:
Flight::halt(); ```php
Flight::halt();
```
You can also specify an optional HTTP status code and message: You can also specify an optional `HTTP` status code and message:
Flight::halt(200, 'Be right back...'); ```php
Flight::halt(200, 'Be right back...');
```
Calling `halt` will discard any response content up to that point. Calling `halt` will discard any response content up to that point. If you want to stop the framework and output the current response, use the `stop` method:
If you want to stop the framework and output the current response, use the `stop` method:
Flight::stop(); ```php
Flight::stop();
```
# Framework Methods # Framework Methods
Flight is designed to be easy to use and understand. The following is the complete set of methods Flight is designed to be easy to use and understand. The following is the complete set of methods for the framework. It consists of core methods, which are regular static methods, and extensible methods, which can be filtered or overridden.
for the framework. It consists of core methods, which are regular static methods, and
extensible methods, which can be filtered or overridden.
## Core Methods ## Core Methods
Flight::map($name, $callback) - Creates a custom framework method. ```php
Flight::map($name, $callback) // Creates a custom framework method.
Flight::register($name, $class, [$params], [$callback]) - Registers a class to a framework method. Flight::register($name, $class, [$params], [$callback]) // Registers a class to a framework method.
Flight::before($name, $callback) // Adds a filter before a framework method.
Flight::before($name, $callback) - Adds a filter before a framework method. Flight::after($name, $callback) // Adds a filter after a framework method.
Flight::path($path) // Adds a path for autoloading classes.
Flight::after($name, $callback) - Adds a filter after a framework method. Flight::get($key) // Gets a variable.
Flight::set($key, $value) // Sets a variable.
Flight::path($path) - Adds a path for autoloading classes. Flight::has($key) // Checks if a variable is set.
Flight::clear([$key]) // Clears a variable.
Flight::get($key) - Gets a variable. ```
Flight::set($key, $value) - Sets a variable.
Flight::has($key) - Checks if a variable is set.
Flight::clear([$key]) - Clears a variable.
## Extensible Methods ## Extensible Methods
Flight::start() - Starts the framework. ```php
Flight::start() // Starts the framework.
Flight::stop() - Stops the framework and sends a response. Flight::stop() // Stops the framework and sends a response.
Flight::halt([$code], [$message]) // Stop the framework with an optional status code and message.
Flight::halt([$code], [$message]) - Stop the framework with an optional status code and message. Flight::route($pattern, $callback) // Maps a URL pattern to a callback.
Flight::redirect($url, [$code]) // Redirects to another URL.
Flight::route($pattern, $callback) - Maps a URL pattern to a callback. Flight::render($file, [$data], [$key]) // Renders a template file.
Flight::error($exception) // Sends an HTTP 500 response.
Flight::redirect($url, [$code]) - Redirects to another URL. Flight::notFound() // Sends an HTTP 400 response.
Flight::etag($id, [$type]) // Performs ETag HTTP caching.
Flight::render($file, [$data], [$key]) - Renders a template file. Flight::lastModified($time) // Performs last modified HTTP caching.
Flight::json($data) // Sends a JSON response.
Flight::error($exception) - Sends an HTTP 500 response. ```
Flight::notFound() - Sends an HTTP 400 response.
Flight::etag($id, [$type]) - Performs ETag HTTP caching.
Flight::lastModified($time) - Performs last modified HTTP caching.
Flight::json($data) - Sends a JSON response.
Any custom methods added with `map` and `register` can also be filtered. Any custom methods added with `map` and `register` can also be filtered.

Loading…
Cancel
Save