Merge branch 'master' into feature/message-pattern-bind-transport

Author: barbarosh

browserslist renamed to .browserslistrc

@@ -0,0 +1,39 @@
+name: Lighthouse
+
+on:
+  pull_request:
+    paths-ignore:
+    - 'content/**/*.md'
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+
+    steps:
+      - uses: actions/checkout@v1
+      - name: Use Node.js 12.x
+        uses: actions/setup-node@v1
+        with:
+          node-version: 12.x
+      # Build needs around 400 seconds on Netlify.
+      # We can not rely on "Waiting for 200", since the user
+      # might push another commit to an existing PR, meaning
+      # the deploy preview is already online.
+      - name: Sleep 400 seconds
+        run: sleep 400
+      - name: Waiting for 200 from the Netlify Preview
+        uses: jakepartusch/wait-for-netlify-action@v1
+        id: wait-for-netflify-preview
+        with:
+          site_name: 'docs-nestjs'
+          max_timeout: 600
+      - name: Run Lighthouse on urls and validate with lighthouserc
+        uses: treosh/lighthouse-ci-action@v2
+        with:
+          urls: |
+            ${{ steps.wait-for-netflify-preview.outputs.url }}
+            ${{ steps.wait-for-netflify-preview.outputs.url }}/first-steps
+          runs: 5
+          configPath: './lighthouserc.json'
+          uploadArtifacts: true
+          temporaryPublicStorage: true

.github/workflows/lighthouse.yml

@@ -1 +1 @@
-12.16.3
+12.18.3

.nvmrc

@@ -131,7 +131,7 @@
   "schematics": {
     "@schematics/angular:component": {
       "prefix": "app",
-      "styleext": "scss"
+      "style": "scss"
     },
     "@schematics/angular:directive": {
       "prefix": "app"

angular.json

@@ -58,7 +58,7 @@ Read the sections on [Workspaces](/cli/monorepo) and [Libraries](/cli/libraries)
 
 <app-banner-courses></app-banner-courses>
 
-### CLI command syntax
+#### CLI command syntax
 
 All `nest` commands follow the same format:
 
@@ -80,7 +80,7 @@ $ nest n my-nest-project -d
 
 Most commands, and some options, have aliases. Try running `nest new --help` to see these options and aliases, and to confirm your understanding of the above constructs.
 
-### Command overview
+#### Command overview
 
 Run `nest <command> --help` for any of the following commands to see command-specific options.
 

content/cli/overview.md

@@ -10,7 +10,7 @@ A Nest application is a **standard** TypeScript application that needs to be com
 
 This goal is accomplished through a combination of the `nest` command, a locally installed TypeScript compiler, and `package.json` scripts. We describe how these technologies work together below. This should help you understand what's happening at each step of the build/execute process, and how to customize that behavior if necessary.
 
-### The nest binary
+#### The nest binary
 
 The `nest` command is an OS level binary (i.e., runs from the OS command line). This command actually encompasses 3 distinct areas, described below. We recommend that you run the build (`nest build`) and execution (`nest start`) sub-commands via the `package.json` scripts provided automatically when a project is scaffolded (see [typescript starter](https://github.com/nestjs/typescript-starter) if you wish to start by cloning a repo, instead of running `nest new`).
 
@@ -30,7 +30,7 @@ See the [nest start](https://docs.nestjs.com/cli/usages#nest-start) documentatio
 
 The `nest generate` commands, as the name implies, generate new Nest projects, or components within them.
 
-### Package scripts
+#### Package scripts
 
 Running the `nest` commands at the OS command level requires that the `nest` binary be installed globally. This is a standard feature of npm, and outside of Nest's direct control. One consequence of this is that the globally installed `nest` binary is **not** managed as a project dependency in `package.json`. For example, two different developers can be running two different versions of the `nest` binary. The standard solution for this is to use package scripts so that you can treat the tools used in the build and execute steps as development dependencies.
 
@@ -54,11 +54,11 @@ These commands use npm's script running capabilities to execute `nest build` or
 
 For most developers/teams, it is recommended to utilize the package scripts for building and executing their Nest projects. You can fully customize the behavior of these scripts via their options (`--path`, `--webpack`, `--webpackPath`) and/or customize the `tsc` or webpack compiler options files (e.g., `tsconfig.json`) as needed. You are also free to run a completely custom build process to compile the TypeScript (or even to execute TypeScript directly with `ts-node`).
 
-### Backward compatibility
+#### Backward compatibility
 
 Because Nest applications are pure TypeScript applications, previous versions of the Nest build/execute scripts will continue to operate. You are not required to upgrade them. You can choose to take advantage of the new `nest build` and `nest start` commands when you are ready, or continue running previous or customized scripts.
 
-### Migration
+#### Migration
 
 While you are not required to make any changes, you may want to migrate to using the new CLI commands instead of using tools such as `tsc-watch` or `ts-node`. In this case, simply install the latest version of the `@nestjs/cli`, both globally and locally:
 

content/cli/scripts.md

@@ -160,7 +160,7 @@ Updates `@nestjs` dependencies in the `package.json` `"dependencies"` list to th
 | Option    | Description                                                              |
 | --------- | ------------------------------------------------------------------------ |
 | `--force` | Do **upgrade** instead of update <br/>Alias `-f`                         |
-| `--tag`   | Update to tagged version (use `@latest`, `@<tag>`, etc) <br/>Alias `-wt` |  |
+| `--tag`   | Update to tagged version (use `@latest`, `@<tag>`, etc) <br/>Alias `-t` |  |
 
 #### nest info
 

content/cli/usages.md

@@ -442,37 +442,38 @@ export class CatsController {
   }
 }
 @@switch
-import { Controller, Get, Query, Post, Body, Put, Param, Delete } from '@nestjs/common';
+import { Controller, Get, Query, Post, Body, Put, Param, Delete, Bind } from '@nestjs/common';
 
 @Controller('cats')
 export class CatsController {
   @Post()
   @Bind(Body())
-  create(@Body() createCatDto) {
+  create(createCatDto) {
     return 'This action adds a new cat';
   }
 
   @Get()
   @Bind(Query())
-  findAll(@Query() query) {
+  findAll(query) {
+    console.log(query);
     return `This action returns all cats (limit: ${query.limit} items)`;
   }
 
   @Get(':id')
   @Bind(Param('id'))
-  findOne(@Param('id') id) {
+  findOne(id) {
     return `This action returns a #${id} cat`;
   }
 
   @Put(':id')
   @Bind(Param('id'), Body())
-  update(@Param('id') id, @Body() updateCatDto) {
+  update(id, updateCatDto) {
     return `This action updates a #${id} cat`;
   }
 
   @Delete(':id')
   @Bind(Param('id'))
-  remove(@Param('id') id) {
+  remove(id) {
     return `This action removes a #${id} cat`;
   }
 }

content/controllers.md

@@ -5,7 +5,7 @@ Nest is built around a language feature called **decorators**. Decorators are a
 <blockquote class="external">
   An ES2016 decorator is an expression which returns a function and can take a target, name and property descriptor as arguments.
   You apply it by prefixing the decorator with an <code>@</code> character and placing this at the very top of what
-  you are trying to decorate. Decorators can be defined for either a class or a property.
+  you are trying to decorate. Decorators can be defined for either a class, a method or a property.
 </blockquote>
 
 #### Param decorators

content/custom-decorators.md

@@ -41,7 +41,7 @@
     },
     {
       "logo": "/assets/logo/sanofi.png",
-      "url": "https://www.sanofi.com/"
+      "url": "https://github.com/Sanofi-IADC"
     },
     {
       "logo": "https://nestjs.com/img/valor-software.png",
@@ -151,6 +151,26 @@
       "logo": "/assets/logo/bedu.svg",
       "url": "https://bedu.org",
       "width": "100px"
+    },
+    {
+      "logo": "/assets/logo/shopback.png",
+      "url": "https://shopback.com",
+      "width": "100px"
+    },
+    {
+      "logo": "/assets/logo/facile.png",
+      "url": "https://www.facile.it",
+      "width": "100px"
+    },
+    {
+      "logo": "/assets/logo/interfacewerk.png",
+      "url": "https://interfacewerk.de",
+      "width": "130px"
+    },
+    {
+      "logo": "/assets/logo/ottonova.png",
+      "url": "https://www.ottonova.de",
+      "width": "130px"
     }
   ],
   "Body": [
@@ -194,6 +214,10 @@
     "https://creatorsdaily.com",
     "https://autoscar.com.br",
     "https://www.mediktiv.com",
-    "https://harmonize.health"
+    "https://harmonize.health",
+    "https://accerlery.be",
+    "https://www.facile.it",
+    "https://shopback.com",
+    "https://www.ottonova.de"
   ]
 }