Node.js
cd existing_repo | |
git remote rename origin old-origin | |
git remote add origin https://gitlab.com/newproject | |
git push -u origin --all | |
git push -u origin --tags |
let obj = {a:'b', c:{d:'e', f:{g:'h'}}} | |
let obj1 = {...obj} | |
// let obj2 = obj | |
// let obj1 = Object.assign({}, obj) | |
obj1.a = 'b1' |
Answer: All APIs of Node.js library are aynchronous that is non-blocking. It essentially means a Node.js based server never waits for a API to return data. Server moves to next API after calling it and a notification mechanism of Events of Node.js helps server to get response from the previous API call.
Source: tutorialspoint.com
{ | |
"security.workspace.trust.untrustedFiles": "open", | |
"workbench.iconTheme": "vscode-icons", | |
"workbench.colorTheme": "Monokai Vibrant", | |
"explorer.confirmDelete": false, | |
"workbench.startupEditor": "newUntitledFile", | |
"terminal.integrated.fontFamily": "'DroidSansMono Nerd Font'", | |
"editor.fontFamily": "FiraCode Nerd Font", | |
"editor.fontLigatures": true, | |
"editor.codeActionsOnSave": { |
tree -I node_modules -L 2 | pbcopy |
- Always use PUBLIC_URL in browserRouter as basename or while giving path to images.
Gives the reviewer some context about the work and why this change is being made, the WHY you are doing this. This field goes more into the product perspective.
Provide a detailed description of how exactly this task will be accomplished. This can be something technical. What specific steps will be taken to achieve the goal? This should include details on service integration, job logic, implementation, etc.
This is where becomes technical. Here is where you can be more focused on the engineering side of your solution. Include information about the functionality they are adding or modifying, as well as any refactoring or improvement of existing code.
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.
- Follow standard conventions.
- Keep it simple stupid. Simpler is always better. Reduce complexity as much as possible.
- Boy scout rule. Leave the campground cleaner than you found it.
- Always find root cause. Always look for the root cause of a problem.