Fix direct loaded middlewares order of registering

Author: MichalLytek

src/RoutingControllers.ts

@@ -95,8 +95,7 @@ export class RoutingControllers {
         this.metadataBuilder
             .buildMiddlewareMetadata(classes)
             .filter(middleware => middleware.global && middleware.type === type)
-            .sort((middleware1, middleware2) => middleware1.priority - middleware2.priority)
-            .reverse()
+            .sort((middleware1, middleware2) => middleware2.priority - middleware1.priority)
             .forEach(middleware => this.driver.registerMiddleware(middleware));
 
         return this;

src/index.ts

@@ -215,7 +215,7 @@ export function createExecutor(driver: Driver, options: RoutingControllersOption
     new RoutingControllers(driver, options)
         .initialize()
         .registerInterceptors(interceptorClasses)
-        .registerMiddlewares("before")
+        .registerMiddlewares("before", middlewareClasses)
         .registerControllers(controllerClasses)
         .registerMiddlewares("after", middlewareClasses); // todo: register only for loaded controllers?
 }

src/metadata-builder/MetadataArgsStorage.ts

@@ -64,9 +64,9 @@ export class MetadataArgsStorage {
      * Filters registered middlewares by a given classes.
      */
     filterMiddlewareMetadatasForClasses(classes: Function[]): MiddlewareMetadataArgs[] {
-        return this.middlewares.filter(ctrl => {
-            return classes.filter(cls => ctrl.target === cls).length > 0;
-        });
+        return classes
+            .map(cls => this.middlewares.find(mid => mid.target === cls))
+            .filter(midd => midd !== undefined); // this might be not needed if all classes where decorated with `@Middleware`
     }
 
     /**