| #! /bin/bash | |
| # | |
| # USAGE: | |
| # orphan [-dv] filename | |
| # | |
| # OPTIONS: | |
| # -d delete the file if it is an orphan | |
| # -f force (ie, don't prompt) | |
| # -h display help text | |
| # -v verbose |
| #!/bin/bash | |
| file=$1 | |
| test -z $file && echo "file required." 1>&2 && exit 1 | |
| git filter-branch -f --index-filter "git rm -r --cached $file --ignore-unmatch" --prune-empty --tag-name-filter cat -- --all | |
| git ignore $file | |
| git add .gitignore | |
| git commit -m "Add $file to .gitignore" |
#Public Data Sources
##Legislative
Important: At the time of writing (2019-11-11) Immutable.js is effectively abandonware, so I can no longer recommend anyone to follow the advice given here. I'll leave the article here for posterity, since it's still getting some traffic.
Functional programming principles and with it immutable data are changing the way we write frontend applications. If the recent de-facto frontend stack of React and Redux feels like it goes perfectly together with immutable data, that's because it's specifically designed for that.
There's several interesting implementations of immutable data for JavaScript, but here I'll be focusing on Facebook's own Immutable.js, and specifically on one of i
