Merge pull request #1112 from 2Kable/master

docs: add NestHybridApplicationOptions documentation

Author: kamilmysliwiec

content/faq/hybrid-application.md

@@ -34,3 +34,14 @@ const microserviceRedis = app.connectMicroservice<MicroserviceOptions>({
 await app.startAllMicroservicesAsync();
 await app.listen(3001);
 ```
+
+#### Sharing configuration
+
+By default a hybrid application will not inherit global pipes, interceptors, guards and filters configured for the main (HTTP-based) application.
+To inherit these configuration properties from the main application, set the `inheritAppConfig` property in the second argument (an optional options object) of the `connectMicroservice()` call, as follow:
+
+```typescript
+const microservice = app.connectMicroservice({
+  transport: Transport.TCP
+}, { inheritAppConfig: true });
+```

content/guards.md

@@ -115,7 +115,7 @@ const app = await NestFactory.create(AppModule);
 app.useGlobalGuards(new RolesGuard());
 ```
 
-> warning **Notice** In the case of hybrid apps the `useGlobalGuards()` method doesn't set up guards for gateways and micro services. For "standard" (non-hybrid) microservice apps, `useGlobalGuards()` does mount the guards globally.
+> warning **Notice** In the case of hybrid apps the `useGlobalGuards()` method doesn't set up guards for gateways and micro services by default (see [Hybrid application](/faq/hybrid-application) for information on how to change this behavior). For "standard" (non-hybrid) microservice apps, `useGlobalGuards()` does mount the guards globally.
 
 Global guards are used across the whole application, for every controller and every route handler. In terms of dependency injection, global guards registered from outside of any module (with `useGlobalGuards()` as in the example above) cannot inject dependencies since this is done outside the context of any module. In order to solve this issue, you can set up a guard directly from any module using the following construction: