Drupal Flight Control - Documentation

See Drupal Flight Control

This is the central point to get some information around the Flight Control project.
If you have questions or recommendations, please let me know.

Quick start

Development info / guidelines


Errors are the oldest form of error handling in PHP dating all the way back to PHP 3. Trigger_error is still useful in certain very limited circumstances owing to the fact that, unlike exceptions, errors cannot be caught or if they don't stop the system then code continues on the line following trigger_error. Drupal primarily makes use of Exceptions and assertions, using errors only when necessary to cause an immediate halt of the system.


Exceptions are the preferred method of fault handling in Drupal. They should be used in all cases but two.

Assertion of Valid Calling Code.

(Note: The code which implements this has not been finalized and added to core. See https://www.drupal.org/node/2408013 )


This assertion checks the calling method's namespace for a match with the called method's namespace, or with a scope argument. The assertion returns true if there is a match, or if the caller is within a child namespace of the called method. It is defined in the supporting Assertions class.

Contributing to DrupalCI


The containers can be found in the /containers subdirectory of the DrupalCI: Test Runner project. Contributors should use the production branch, which contains the latest stable code.


(Note - the code implementing these features is still under development and has not been merged into core. See https://www.drupal.org/node/2408013)

An assertion is a special type of error function that is used during the development of code. It has existed in PHP since version 4 and is being introduced to Drupal as of version 8 in order to help monitor interactions between core code and third party modules.


Subscribe with RSS Subscribe to RSS - Advanced