- generate controllers
nest g controller items@greglim81 @danielgara https://github.com/PracticalBooks/Practical-Nest
Newman, S. - Building microservices
npm install --save hbs
Figure 5-1. Online Store software architecture. Let’s have a quick analysis of this architecture: • On the left, we have clients (users of our application e.g., browsers in mobile/desktop devices). Clients connect to the application through the Hypertext Transfer Protocol (HTTP). HTTP gives users a way to interact with our web application. • On the right, we have the server where we place our application code. • Clients’ interactions are connected to the main application file (main.ts). This file loads the root module (AppModule), which internally will load other modules (described in Chapter 10), and those modules pass the clients’ interactions to the controllers. • Controllers (described in Chapter 7) execute the clients’ interactions based on the specific requested routes, i.e. (“/products”) or (“/cart”) routes. Controllers communicate with models (described in Chapter 13), and pass information to the views (described in Chapter 4), which are finally delivered to the clients as HTML, CSS, and JavaScript code
npm install hbs-utils
Controllers are responsible for handling incoming requests and returning responses to the client. Controllers can group related request handling logic into a single class. For example, a UserController class might handle all incoming requests related to users, including showing, creating, updating, and deleting users.
the (2019 - Thomas, D., & Hunt, A. - The Pragmatic Programmer: your journey to mastery)
-
TIP: As a software developer, a good strategy is to create a document with architectural rules and share that document with your team (if you have one). You can make that document in the project repository wiki (if you have one). Encourage all the members to read that document. A first rule that you can include in that document could be: “controllers should only pass an associative array called viewData to the views”. These simple rules will save you a lot of time and a lot of headaches; believe us, Daniel always creates a document like that for all his projects, and he encourages his students to do it in their projects
-
There is a good story about “The Broken Window Theory” described in the (2019 - Thomas, D., & Hunt, A. - The Pragmatic Programmer: your journey to mastery) book
-
Always use a coding standard tool, formatter, static code analysis tool, or even a combination of them in your projects. It will save you a lot of time and improve the code quality. In addition, you will find linters available for most programming languages. Besides, include a rule in your architectural rules document mentioning that all code changes should be previously verified using these tools. You can even automate this process (with a pipeline or CI/CD strategy). However, this is out of the scope of this book
-
add linter formatter for hbs
-
Consider Using
nest-i18n- fro internationalization -
TIP: Always try to access your entity/model attributes through getters and setters. It will make it easier to add functionalities in the future. You can even include a new rule saying that entities/models’ attributes must be accessed through their corresponding getters and setters (in your architectural rules document)
A progressive Node.js framework for building efficient and scalable server-side applications.
Nest framework TypeScript starter repository.
$ npm install# development
$ npm run start
# watch mode
$ npm run start:dev
# production mode
$ npm run start:prod# unit tests
$ npm run test
# e2e tests
$ npm run test:e2e
# test coverage
$ npm run test:covNest is an MIT-licensed open source project. It can grow thanks to the sponsors and support by the amazing backers. If you'd like to join them, please read more here.
- Author - Kamil Myśliwiec
- Website - https://nestjs.com
- Twitter - @nestframework
Nest is MIT licensed.