diff --git a/README.md b/README.md index 4a11574471..400fe960e9 100644 --- a/README.md +++ b/README.md @@ -1,5 +1,5 @@
[travis-image]: https://api.travis-ci.org/nestjs/nest.svg?branch=master @@ -7,7 +7,7 @@ [linux-image]: https://img.shields.io/travis/nestjs/nest/master.svg?label=linux [linux-url]: https://travis-ci.org/nestjs/nest -A progressive Node.js framework for building efficient and scalable server-side applications, heavily inspired by Angular.
+A progressive Node.js framework for building efficient and scalable server-side applications, heavily inspired by Angular.
diff --git a/content/controllers.md b/content/controllers.md index b74a2b6ce7..d055748402 100644 --- a/content/controllers.md +++ b/content/controllers.md @@ -58,7 +58,7 @@ This method will return a 200 status code and the associated response, which in
@Res()
decorator in the method handler signature (e.g., findAll(@Res() response)
). With this approach, you have the ability (and the responsibility), to use the native response handling methods exposed by that object. For example, with Express, you can construct responses using code like response.status(200).send()
+ We can use the library-specific (e.g., Express) response object, which can be injected using the @Res()
decorator in the method handler signature (e.g., findAll(@Res() response)
). With this approach, you have the ability (and the responsibility), to use the native response handling methods exposed by that object. For example, with Express, you can construct responses using code like response.status(200).send()
@grpc/proto-loader
options. They are well-described
here.
@@ -67,7 +67,7 @@ There are a bunch of available options that determine a transporter behavior.
queueOptions
socketOptions
Made by
Kamil Myśliwiec
diff --git a/src/app/homepage/menu/menu-item/menu-item.component.html b/src/app/homepage/menu/menu-item/menu-item.component.html
index 3efd8b0817..e3bb40a4f6 100644
--- a/src/app/homepage/menu/menu-item/menu-item.component.html
+++ b/src/app/homepage/menu/menu-item/menu-item.component.html
@@ -20,7 +20,7 @@
- TypeScript 2.2 adds support for the ECMAScript 2015 mixin class pattern.
+ TypeScript 2.2 adds support for the ECMAScript 2015 mixin class pattern.
This pattern's quite useful since it's not easy to pass custom arguments to some Nest application building blocks, such as interceptors or guards.
The mixin classes have much more applications, but here we're gonna focus on this single use-case.
The {{ title }}
{{ item.title }}
-
{{ item.icon }}
@@ -44,7 +44,7 @@ {{ title }}
{{ title }}
-
{{ icon }}
diff --git a/src/app/homepage/pages/advanced/mixin-components/mixin-components.component.html b/src/app/homepage/pages/advanced/mixin-components/mixin-components.component.html
index cdfd51d592..769dd8dbbc 100644
--- a/src/app/homepage/pages/advanced/mixin-components/mixin-components.component.html
+++ b/src/app/homepage/pages/advanced/mixin-components/mixin-components.component.html
@@ -2,7 +2,7 @@
Mixin Class
This chapter applies only to TypeScript
This chapter applies only to TypeScript
mixin()
function returns the class, so you can use it in the same manner as a plain, self-created classes.
The schema stitching is a feature that allows creating a single GraphQL schema from multiple underlying GraphQL APIs. You - can read more about it here. + can read more about it here.
To add the ability to proxy fields between schemas, you need to create additional resolvers between them. Let's have a look on the example from the Apollo documentation: + target="_blank" rel="nofollow">Apollo documentation:
{{ stitchingExample }}
@@ -31,13 +31,13 @@
{{ createSchema }}
In order to merge schemas, we have used mergeSchemas()
function (read more). Moreover, you may notice chirpsSchema
and linkTypeDefs
variables.
+ target="_blank" rel="nofollow">read more). Moreover, you may notice chirpsSchema
and linkTypeDefs
variables.
They're copied & pasted directly from the Apollo documentation.
+ target="_blank" rel="nofollow">Apollo documentation.
{{ chirpsSchema }}
That's all.
- \ No newline at end of file + diff --git a/src/app/homepage/pages/microservices/custom-transport/custom-transport.component.html b/src/app/homepage/pages/microservices/custom-transport/custom-transport.component.html index d5328ca529..918d314287 100644 --- a/src/app/homepage/pages/microservices/custom-transport/custom-transport.component.html +++ b/src/app/homepage/pages/microservices/custom-transport/custom-transport.component.html @@ -2,7 +2,7 @@
The Nest has a built-in transport via TCP and Redis, but other communication schemes can be implemented with CustomTransportStrategy
interface.
- For demonstration purposes, we're going to port the RabbitMQ transport strategy using ampqlib library.
+ For demonstration purposes, we're going to port the RabbitMQ transport strategy using ampqlib library.
@@ -28,8 +28,8 @@
{{ setupServer }}
- The RabbitMQ server's listening to messages.
- Now it's time to create a client class, which shall extends the abstract ClientProxy
class.
+ The RabbitMQ server's listening to messages.
+ Now it's time to create a client class, which shall extends the abstract ClientProxy
class.
To make it work, we only have to override sendSingleMessage()
method.
Hint To make unit testing easy, you can provide a custom component instead of creating the instance directly in the class body.- \ No newline at end of file + diff --git a/tools/transforms/templates/who-uses.template.html b/tools/transforms/templates/who-uses.template.html index 97dc305795..9491b9775c 100644 --- a/tools/transforms/templates/who-uses.template.html +++ b/tools/transforms/templates/who-uses.template.html @@ -5,7 +5,7 @@
{$ company $} | +{$ company $} |
and a lot more but we don't have enough time to update above list. Feel free to create a pull + target="_blank">pull request though!
-{% endblock %} \ No newline at end of file +{% endblock %}