• Optional bind keys with question mark parameter
• Allow binding of named templates without specifying name
• Allow templates to be referenced outside of the tree path
• Unit test coverage improved
• CodeSniffer warnings resolved

All originally scoped features are now implemented, but some real world use-cases must be tested before we get close to a production release.

• Invalid bind properties are caught
• Bind attributes are tidied
• Template attributes are tidied
• Templates are removed from document

• Exceptions thrown when expected bind attribute is not found
• Data binding on existing elements improved
• Todo list test written and passing

• Data is bound on existing elements
• Bind function split into in-document and in-template
• More tests

Bindable introduces the next feature: dynamic data binding.

Now that this repository has been prototyped, it has reached full test coverage. Let’s keep it at 100% as new features are introduced.

The readme file touches on the three main features of the library: binding, custom elements and template elements.

Components can contain components. This is now implemented and tested, but may change.

Custom components are now automatically converted into their template HTML.

This first pre-release marks the successful extension of PHP.Gt/Dom with extended behaviour.

• Tests improved
• Standardisation of scope resolution
• Methods wrapped with extended types
• Methods return types standardised
• Dropped templates from documentation - use DomTemplate instead
• Updated code to match StyleGuide
• Introduced CircleCI 2.0
• Upgraded PHPUnit to v6

Build process set up

• PHPUnit
• CircleCI 2.0
• Scrutinizer

All cURL functions mapped from http://php.net/manual/en/ref.curl.php

• Versions of required build software checked
• Build runner runs in the background forever
• Matching file changes detected
• Build software executed when needed

• The BuildRunner class is run from the WebEngine’s bin directory
• JSON file parsed and expanded into TaskList
• TaskList contains multiple Task objects
• Each Task has a number of Requirement objects
• Globs expanded in Task to match all files
• Files are md5 hashed for whatever watch system is decided upon

• All CodeSniffer inspections are resolved.
• The updated PHP.Gt/StyleGuide has been adhered to.
• CircleCI updated to 2.0

As unit test coverage increases, APIs change.

The Input class itself shares its data access methods with the InputData class for ease of use and quick on-the-fly data access.

Accessing data is done using ArrayAccess now, rather than property access, due to the StyleGuide specifying “Only properties should be used when a predefined set of data attributes can be determined”.

The basics are working. The Input class can be constructed from the $_GET, $_POST and $_FILES arrays. with(), without(), withAll() have been tested when calling them on the Input class themselves, and the correct callbacks are called.

This first pre-release marks just enough functionality to implement the rest of the WebEngine.

Allowing named or ordered bindings utilised the new PHP feature of variable arguments, using the ... operator. This new feature, coupled with the shorthand helper methods caused a situation where bindings could be doubly nested.

The introduction of the concept of a QueryCollection meant that longhand API usage was too wordy and had too many steps to perform simple operations.

This release includes a new shorter syntax and due to this syntax being preferred, dropping accessing QueryCollection via ArrayAccess (backwards breaking).

New syntax:

$db = new Client();

$customer = $db->fetch("customer/getById", ["id" => 123]);
$customerList = $db->fetchAll("customer/getInTown", ["town" => "London"]);
$newCustomerId = $db->insert("customer/create", $details);
$updatedCount = $db->update("customer/setDetails", $details);
$deletedCount = $db->delete("customer/deleteOlderThan", ["createdAt" =>new DateTime("-30 days")]);

As in v1 we are not supporting any QueryBuilder or SchemaBuilder, we’re dropping the requirement of Illuminate’s database layer. There was no benefit from the heavy reliance on Reflection, so now it’s been removed and there is only a dependency on PDO itself.

Rewriting existing logic with PSR-7 compatibility

• All DOM class implementations’ methods/properties tested
• UTF-8 compatible
• Level 4 methods (matches, remove, etc.)
• TokenList
• Fully type-hinted to PHP 7.0 capabilities, docblocks used where needed