feature(joins:nested) version up

Author: michaelyali

README.md

@@ -21,7 +21,7 @@
 - Composition of controller methods instead of inheritance (no tight coupling and less surprises)
 - Overriding controller methods with ease.
 - Request validation.
-- Query parameters parsing with filters, pagination, sorting, etc.
+- Query parameters parsing with filters, pagination, sorting, joins, nested joins, etc.
 - Super fast DB query building.
 - Additional handy decorators.
 
@@ -314,7 +314,7 @@ _Syntax:_
 
 > ?join=**relation**||**field1**,**field2**,...
 
-> ?join=**relation1**||**field11**,**field12**,...&join=**relation1**.**relation2**||**field21**,**field22**,...&join=...
+> ?join=**relation1**||**field11**,**field12**,...&join=**relation1**.**nested**||**field21**,**field22**,...&join=...
 
 _Examples:_
 
@@ -324,7 +324,7 @@ _Examples:_
 
 > ?join=**profile**||**firstName**,**email**&join=**notifications**||**content**&join=**tasks**
 
-> ?join=**relation1**&join=**relation1**.**relation2**&join=**relation1**.**relation2**.**relation3**
+> ?join=**relation1**&join=**relation1**.**nested**&join=**relation1**.**nested**.**deepnested**
 
 **_Notice:_** `id` field always persists in relational objects. To use nested relations, the parent level **MUST** be set before the child level like example above.