(by @andrestaltz)
If you prefer to watch video tutorials with live-coding, then check out this series I recorded with the same contents as in this article: Egghead.io - Introduction to Reactive Programming.
git checkout master | |
git pull | |
git checkout branch-4.6.3 | |
git pull | |
git checkout -b issue-924-back | |
git cherry-pick HERE SHA1 of all commits in correct order | |
git push origin issue-924-back |
input { | |
elasticsearch { | |
hosts => ["es0.dev.ukcris"] | |
index => "carenotes_etl" | |
} | |
} | |
output { | |
stdout { | |
codec => rubydebug | |
} |
git checkout master | |
git pull | |
git checkout issue-106 | |
git rebase master | |
# here in case of any conflict fix it | |
# do git add path/to/fixed/file | |
git rebase —continue | |
git push -f origin issue-106 | |
(by @andrestaltz)
If you prefer to watch video tutorials with live-coding, then check out this series I recorded with the same contents as in this article: Egghead.io - Introduction to Reactive Programming.
This article has been given a more permanent home on my blog. Also, since it was first written, the development of the Promises/A+ specification has made the original emphasis on Promises/A seem somewhat outdated.
Promises are a software abstraction that makes working with asynchronous operations much more pleasant. In the most basic definition, your code will move from continuation-passing style:
getTweetsFor("domenic", function (err, results) {
// the rest of your code goes here.