A complete list of RxJS 5 operators with easy to understand explanations and runnable examples.
| [FunctionName("SampleMessageExecutor")] | |
| public static async Task Run( | |
| [ServiceBusTrigger("test-queue", "test-subscription", Connection = "ServiceBusConnectionString")] | |
| MessageReceiver messageReceiver, string lockToken) | |
| { | |
| //the new data is optional | |
| //you can also use CompleteAsync() or DeadletterAsync() | |
| await messageReceiver.AbandonAsync(lockToken, new Dictionary<string, object> | |
| { | |
| {"new-data", "new-value"} |
| #import <Foundation/Foundation.h> | |
| #import "RCTBridgeModule.h" | |
| #define RCT_EXTERN_MODULE(objc_name, objc_supername) \ | |
| RCT_EXTERN_REMAP_MODULE(objc_name, objc_name, objc_supername) | |
| #define RCT_EXTERN_REMAP_MODULE(js_name, objc_name, objc_supername) \ | |
| objc_name : objc_supername \ | |
| @end \ | |
| @interface objc_name (RCTExternModule) <RCTBridgeModule> \ |
| I'll try to illustrate the process for doing this by describing what I do. | |
| First, you get your fork of Akka.NET - everything is cool. | |
| Next, you clone it to your machine. Right now your "origin" is set to your local fork. | |
| If Github for Windows doesn't do this for you automatically, you'll need to add a second remote to your local copy of your Akka.NET repository - one that points to the main repository (akkadotnet/akka.net) | |
| git remote add upstream git@github.com:akkadotnet/akka.net.git | |
| Now let's say you want to add a new feature - first thing you need to do is create a new feature branch. Don't work directly off of dev. |
| var Bar1 = base => class extends base { | |
| componentWillMount(){ | |
| super.componentWillMount(); | |
| console.log('Bar1'); | |
| } | |
| }; | |
| var Bar2 = base => class extends base { | |
| componentWillMount(){ | |
| super.componentWillMount(); |
Hello, visitors! If you want an updated version of this styleguide in repo form with tons of real-life examples… check out Trellisheets! https://github.com/trello/trellisheets
“I perfectly understand our CSS. I never have any issues with cascading rules. I never have to use !important or inline styles. Even though somebody else wrote this bit of CSS, I know exactly how it works and how to extend it. Fixes are easy! I have a hard time breaking our CSS. I know exactly where to put new CSS. We use all of our CSS and it’s pretty small overall. When I delete a template, I know the exact corresponding CSS file and I can delete it all at once. Nothing gets left behind.”
You often hear updog saying stuff like this. Who’s updog? Not much, who is up with you?
(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.