Update: As package.elm-lang.org IP address has been changed and is not blocked anymore as far as I know, these proxies have been disabled. If you still need them, add a comment describing why.
Here is how to use the proxies:
Two options:
#include <stdint.h> | |
#include <stdio.h> | |
#include <stdlib.h> | |
// munged from https://github.com/simontime/Resead | |
namespace sead | |
{ | |
class Random | |
{ |
Update: As package.elm-lang.org IP address has been changed and is not blocked anymore as far as I know, these proxies have been disabled. If you still need them, add a comment describing why.
Here is how to use the proxies:
Two options:
@override | |
Widget build(BuildContext context) { | |
if (_base64 == null) | |
return new Container(); | |
Uint8List bytes = BASE64.decode(_base64); | |
return new Scaffold( | |
appBar: new AppBar(title: new Text('Example App')), | |
body: new ListTile( | |
leading: new Image.memory(bytes), | |
title: new Text(_base64), |
Example of deployment process which I use in my Nuxt.js projects. I usually have 3 components running per project: admin-panel SPA, nuxt.js renderer and JSON API.
This manual is relevant for VPS such as DigitalOcean.com or Vultr.com. It's easier to use things like Now for deployment but for most cases VPS gives more flexebillity needed for projects bigger than a landing page.
UPD: This manual now compatible with [email protected]. For older versions deployment, see revision history.
Let's assume that you have entered fresh installation of Ubuntu instance via SSH. Let's rock:
import { createStore, applyMiddleware, combineReducers } from "redux"; | |
import thunk from "redux-thunk"; | |
import { userReducer, UserAction, UserState } from "./user"; | |
import { handshakeReducer, HandShakeAction, HandshakeState } from "./handshake"; | |
import { productInfoReducer, ProductInfoAction, ProductInfoState } from "./product"; | |
import { circleReducer, CircleAction, CircleState } from "./circle"; | |
export const store = createStore(combineReducers({ | |
user: userReducer, |
import {Action, ActionCreator, Dispatch} from 'redux'; | |
import {ThunkAction} from 'redux-thunk'; | |
// Redux action | |
const reduxAction: ActionCreator<Action> = (text: string) => { | |
return { | |
type: SET_TEXT, | |
text | |
}; | |
}; |
let mapleader = "," | |
if &compatible | |
set nocompatible " Be iMproved | |
endif | |
call plug#begin('~/.vim/plugged') | |
Plug 'tpope/vim-fugitive' | |
Plug 'airblade/vim-gitgutter' |
This Gist provides some code examples of how to implement WebSocket stream handling using a Redux middleware. Please be aware that this is only provided as an example and that critical things like exception handling have not been implemented.
A more complete version has been packaged, tested, and is available on GitHub as redux-websocket. This library has also been published to npm at @giantmachines/redux-websocket
.
This module represents the foundation of the middleware and implements the ideas presented above. The exported function is used during the creation of the Redux store (see the following snippet).
// @flow | |
declare type Reducer<S, A> = (state: S, action: A) => S; | |
type ExtractState = <S>(r: Reducer<S, *>) => S; | |
declare function combineReducers<O, A>(reducers: O): Reducer<$ObjMap<O, ExtractState>, A>; | |
type State = { | |
name: string, | |
age: number | |
}; |