Feature/custom decorators

README.md

@@ -83,7 +83,8 @@ Next, let's create a [Repository Service](#repository-service) for it:
 ```typescript
 import { Injectable } from '@nestjs/common';
 import { InjectRepository } from '@nestjs/typeorm';
-import { RepositoryService } from '@nestjsx/crud/typeorm';
+import { forTypeORM } from '@nestjsx/crud';
+import RepositoryService = forTypeORM.RepositoryService;
 
 import { Hero } from './hero.entity';
 
@@ -612,32 +613,41 @@ Also, routes options object may have some options for each particular route:
   routes: {
     getManyBase: {
       interceptors: [],
+      decorators: [],
     },
     getOneBase: {
       interceptors: [],
+      decorators: [],
     },
     createOneBase: {
       interceptors: [],
+      decorators: [],
     },
     createManyBase: {
       interceptors: [],
+      decorators: [],
     },
     updateOneBase: {
       interceptors: [],
+      decorators: [],
       allowParamsOverride: true
     },
     deleteOneBase: {
       interceptors: [],
+      decorators: [],
       returnDeleted: true
     },
   }
 }
 ```
 
 `interceptors` - an array of your custom interceptors  
+`decorators` - an array of your custom decorators
 `allowParamsOverride` - whether or not to allow body data be overriten by the URL params on PATH request. Default: `false`  
 `returnDeleted` - whether or not an entity object should be returned in the response body on DELETE request. Default: `false`
 
+**_Notice:_** `decorators` will not move from original ones to override ones
+
 ### Params Options
 
 `CrudOptions` object may have `params` parameter that will be used for validation sake of you URL params and for defining a slug param (if it differs from `id` that is used by default).