Updated for v0.2.0

Author: Alistair Kearney

CHANGELOG.md

@@ -3,12 +3,16 @@ All notable changes to this project will be documented in this file.
 This project adheres to [Semantic Versioning](http://semver.org/).
 
 ## [Unreleased]
+None
+
+## [0.2.0] - 2016-05-03
 #### Added
 - Transformer and Transformation classes.
 - Added APIFrameworkJSONRendererAppendTransformations delegate
 - Added phpunit to composer require-dev
 - Added unit tests for Transformation code
 - Controller names are based on full page path (#5)
+- Using PSR-4 folder structure for controllers. Controllers must have a namespace. (#7)
 
 #### Fixed
 - Checking that controller actually exists before trying to include it (#6)
@@ -33,5 +37,6 @@ This project adheres to [Semantic Versioning](http://semver.org/).
 - Initial release
 - Added Symphony PDO as requirement
 
-[Unreleased]: https://github.com/pointybeard/api_framework/compare/v0.1.1...master
+[Unreleased]: https://github.com/pointybeard/api_framework/compare/v0.2.0...integration
+[0.1.2]: https://github.com/pointybeard/api_framework/compare/v0.1.1...v0.2.0
 [0.1.1]: https://github.com/pointybeard/api_framework/compare/v0.1.0...v0.1.1

README.md

@@ -131,14 +131,16 @@ Lastly, call the render method (which is inherited) to generate the output. E.g.
 
     return $this->render($response, ['data' => 'some output']);
 
-A controllers class and file name are the same. It is based on the full path to your page.
+A controllers class and file name are the same. Each controller must sit in a folder path that matches your page path.
 
-For example, if you had a page called "entry", and you wanted to provide PUT, POST, PATCH and DELETE functionality, name your controller class "ControllerEntry" and the file `ControllerEntry.php`. If that same page was then a child of a page called "parent", than both the class and file names would be "ControllerParentEntry" instead.
+For example, if you had a page called "entry", and you wanted to provide PUT, POST, PATCH and DELETE functionality, name your controller class "ControllerEntry" and the file `ControllerEntry.php`. It should be placed in `/workspace/controllers`. If that same page was then a child of a page called "parent", you must create a new folder called `parent` inside `/workspace/controllers`. Place `ControllerEntry` in this new folder. Be sure to adjust its namespace accordingly. **Note: Be sure to rebuild your composer autoloader (`composer dumpautoload`) whenever you move or create a new Controller.**
 
 Here is an example of a completed controller:
 
     <?php
 
+    namespace Symphony\ApiFramework\Controllers;
+
     use Symfony\Component\HttpFoundation\Request;
     use Symfony\Component\HttpFoundation\Response;
     use Symphony\ApiFramework\Lib\AbstractController;