| // Elements with `data-observe` toggle `data-visible` | |
| // between `true` and `false` | |
| if ('IntersectionObserver' in window) { | |
| const callback = (entries, observer) => { | |
| entries.forEach(entry => { | |
| entry.target.setAttribute('data-visible', entry.isIntersecting) | |
| }) | |
| } | |
With the release of Node 6.0.0, the surface of code that needs transpilation to use ES6 features has been reduced very dramatically.
This is what my current workflow looks like to set up a minimalistic and fast microservice using micro and async + await.
The following guide will show you how to deploy a simple microservice written in JavaScript using 𝚫 now.
It uses Open Source tools that are widely available, tested and understood:
| function* runTimer(getState) { | |
| while(yield take('START')) { | |
| while(true) { | |
| const {stop, tick} = yield race({ | |
| stop : take('STOP'), | |
| tick : call(wait, ONE_SECOND); | |
| }) | |
| if ( !stop ) { | |
| yield put(actions.tick()); |
Many times you want to fiddle around with amazing tech like React or RustLang that are pushing the boundaries of what is possible. Back to the real world, there are still cases where an Excel sheet is more appropiate. Especially when companies previously built around it and have existing legacy code. Maybe the end user simply wants just one file to send per mail or move around. For this, Excel is still a viable option.
So for those people that are struggling with the limited vba language, this documentation aims to improve just a little bit of the developer experience while creating excel applications.
This may also partially apply to other office suite applications.
Feel free to send pull request with your Excel code that you found helpful or documentation additions.
Custom recipe to get full Node.js Cloud Environment in DigitalOcean Dokku droplet running from scratch. Yes. Your own Heroku for $5 per month.
I use this gist to keep track of the important configuration steps required to have a functioning system after fresh install.
When you have executed that's all step by step you will get a new working and stable system which is ready to host & serve your Node.js application and databases.
When you spectate a game in League of Legends, you tell the client to use a HTTP server, and make HTTP requests to it to retrieve data in chunks which make up a game. But what if you could return back the exact same data at a later time, simulating the spectate but viewing it at anytime? That's the concept behind replays and that's how they work.
There is some behavior in the API which I do not fully understand yet, so there are if statements to catch these edge cases.
Before you can even get the game's metadata, you'll need to retrieve necessary information for the game. This call is part of the official Riot Games API.
/observer-mode/rest/consumer/getSpectatorGameInfo/{platformId}/{summonerId}
Why would you want to do this? Because you often don't need more. It's nice to not have to think about your "router" as this big special thing.
Instead, with this approch, your app's current pathname is just another piece of state, just like anything else.
This also means that when doing server-side rendering of a redux app, you can just do:
var app = require('your/redux/app')
var React = require('react')
| import React, { PropTypes } from 'react'; | |
| import { TransitionMotion, spring } from 'react-motion'; | |
| /** | |
| * One example of using react-motion (0.3.0) within react-router (v1.0.0-rc3). | |
| * | |
| * Usage is simple, and really only requires two things–both of which are | |
| * injected into your app via react-router–pathname and children: | |
| * | |
| * <RouteTransition pathname={this.props.pathname}> |
| const composedCreateStore = compose( | |
| applyMiddleware( | |
| thunkMiddleware, | |
| dispatchIdMiddleware, | |
| webWorkerMiddleware('/build/worker.js'), | |
| () => promiseMiddleware, | |
| loggerMiddleware | |
| ), | |
| createStore | |
| ); |