ng add @angular-eslint/schematics
npm i eslint-plugin-jasmine -D
And add a new block of rules in overrides for files with *.spec.ts extension:
"overrides": [
...,| .cta-container { | |
| display: flex; | |
| flex-direction: column; | |
| gap: 24px; | |
| padding: 24px; | |
| border: 1px solid rgba(0, 0, 0, 0.1); | |
| } | |
| .cta-content { | |
| display: flex; |
Code is clean if it can be understood easily – by everyone on the team. Clean code can be read and enhanced by a developer other than its original author. With understandability comes readability, changeability, extensibility and maintainability.
Starting a personal node project could be easy; starting a team node project could be challenging.
I am a developer currently working in SEEK Australia.
In my experience, common mistakes developer make when starting a projects are:
| 1. Lấy code mới | |
| - git status (kiểm tra đang ở branch nào) | |
| - git checkout {branch name} (chuyển sang branch cần lấy code về) | |
| - git fetch && git pull origin {branch name} | |
| 2. Tạo branch mới để code | |
| - git checkout {parent branch name} (checkout branch cha của branch chuẩn bị làm, thường là branch master) | |
| - git fetch && git pull origin {parent branch name} | |
| - git checkout -b {branch name} (tạo branch mới từ branch hiện tại (parent branch name)) |