By: @BTroncone
Also check out my lesson @ngrx/store in 10 minutes on egghead.io!
Update: Non-middleware examples have been updated to ngrx/store v2. More coming soon!
Table of Contents
function showDate(){ | |
var date = new Date(), | |
str = date.toUTCString(); | |
return str; | |
} | |
var orig = console.log; | |
console.log = function() { |
By: @BTroncone
Also check out my lesson @ngrx/store in 10 minutes on egghead.io!
Update: Non-middleware examples have been updated to ngrx/store v2. More coming soon!
Table of Contents
Git rebase easy | |
// make sure that you are on your branch | |
git fetch origin | |
git reset $(git merge-base master $(git branch --show-current)) | |
Git download PR into new branch | |
git fetch origin pull/2/head | |
git checkout -b NEW_BRANCH_NAME FETCH_HEAD | |
download and install font from https://github.com/abertsch/Menlo-for-Powerline | |
set your vs code font to: | |
"terminal.external.osxExec": "iterm.app", | |
"terminal.integrated.shell.osx": "/bin/zsh", | |
"terminal.integrated.fontFamily": "Menlo for Powerline", |
https://run.plnkr.co/preview/ckf5hukqg000e3b6aom42idir/ |
A commit should be a wrapper for related changes. For example, fixing two different bugs should produce two separate commits. Small commits make it easier for other developers to understand the changes and roll them back if something went wrong. With tools like the staging area and the ability to stage only parts of a file, Git makes it easy to create very granular commits.
Committing often keeps your commits small and, again, helps you commit only related changes. Moreover, it allows you to share your code more frequently with others. That way it‘s easier for everyone to integrate changes regularly and avoid having merge conflicts. Having large commits and sharing them infrequently, in contrast, makes it hard to solve conflicts.