(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.
# Built application files | |
/*/build/ | |
# Crashlytics configuations | |
com_crashlytics_export_strings.xml | |
# Local configuration file (sdk path, etc) | |
local.properties | |
# Gradle generated files |
(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.
/* | |
* LinkedIn Bulk Accept Invitations Super Magical Hacky Script | |
* | |
* Just past this as a whole into the JavaScrip console on Chrome (or browser of choice) | |
* | |
*/ | |
// function simulating the clicks on checkbox and 'accept' button | |
var catsFromSpace = function(){ | |
console.log("Doing the bulk invite dance"); // Log it, log it real good |
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
import React from 'react'; | |
import 'jscolor'; | |
let uniqueIdCounter = 0; | |
class CustomColorPicker extends React.Component { | |
constructor(){ | |
super(); | |
this.uniqueId = `customColorPickerId${++uniqueIdCounter}` | |
} |
// UPDATE: don't use this. when it re-partitions the list when time moves forward, it does not correctly keep hashes | |
// Use a real merkle tree instead: https://gist.github.com/jlongster/f431b6d75ef29c1a2ed000715aef9c8c | |
import Timestamp from './timestamp'; | |
// This is a compact data structure that keeps track of a list of | |
// hashes (representing messages) over a range of time in order to | |
// figure out what has changed between clients, kinda like a Merkle | |
// tree. It creates "buckets" that represent different time ranges, | |
// and divides time into smaller buckets the more recent they are. The |
9 March, 2019
We were discussing with @erusev what we can do with async operation when using useReducer()
in our application. Our app is simple and we don't want to use a state management library. All our requirements are satisfied with using one root useReducer()
. The problem we are facing and don't know how to solve is async operations.
In a discussion with Dan Abramov he recommends Solution 3 but points out that things are fresh with hooks and there could be better ways of handling the problem.