Tmstack
deployed apps
hrs
https://github.com/mckennatim/hrs <markdown>
The React components are just a stateless projection of the state at a given point in time.
ref: - <a href="http://teropa.info/blog/2015/09/10/full-stack-redux-tutorial.html">Full-Stack Redux Tutorial A Comprehensive Guide to Test-First Development with Redux, React, and Immutable Posted on Thursday Sep 10, 2015 by Tero Parviainen (@teropa)</a> - <a href="https://github.com/babel/example-node-server">babel node server</a>
It is a much better idea to, whenever you can, make operations work on the smallest piece (or subtree) of the state possible. What we're talking about is modularization: Have the functionality that deals with a given piece of data deal with only that part of the data, as if the rest didn't exist.
- immutable examples
let state = fromJS({ctrl: {panel: "auto", relay: "on", by: 'forecast'},
cond: {temp: 67, sky: "cloudy"},
forecast: {isSnow: true, when: "now", accum: 10}});
let nextState = state.setIn(['ctrl', 'by'], 'user')
expect(state.getIn(['ctrl', 'by'])).to.equal("forecast")
`['ctrl', 'by']` is the `keypath`
- notes
map creates a new array, foreach doesn't
- client
- install
npm install
- run in dev
webpack-dev-server --port 4444
- deploy
npm run deploy
This runs `"deploy": "set NODE_ENV=production&& webpack -p --config webpack.production.config.js"` creating `dist/app.js`(5 KB) and `dist/vendors.js`(186 KB) which are the only files you need for deployment! `index.htm` looks like this:
<!DOCTYPE html>
hrs
- note: windows requires that deploy string, mostly you see examples like `"deploy": "NODE_ENV=production webpack -p --config webpack.production.config.js"` but that doesn't work in windows.
- server
- install
npm install
- dev server
npm run start
- prod server
npm run build npm run serve
- test
npm run test:watch
- server setup
npm init -y npm install --save-dev babel-core babel-cli babel-preset-es2015 npm install --save-dev mocha chai npm install --save immutable npm install --save-dev chai-immutable
We need to let plug in chai-immutable before any tests are run. That we can do in a little test helper file, which should create next:
test/test_helper.js
import chai from 'chai'; import chaiImmutable from 'chai-immutable'; chai.use(chaiImmutable);
"scripts": {
"start": "nodemon lib/index.js --exec babel-node --presets es2015,stage-2 --watch lib",
"build": "babel lib -d dist --presets es2015,stage-2",
"serve": "node dist/index.js",
"test": "mocha --compilers js:babel-core/register --require ./test/test_helper.js --recursive --slow 4",
"test:watch": "npm run test -- --watch"
},
`nodemon` restarts the server `lib/index.js` whenever the `--watch`ed directory changes. When it resarts it has to transpile all the es6 code to es5.
`build`s an es5 version of your es6 code (in lib) and puts it in /dist
- modules
- verify-addr
- modules
A module that provides an api for a store of addresses kept in the mysql `forecast` db and `locations` table. It has the following fields.
id - raw - a string that may or may not get you the right address st - the state of raw address - the string returned by google results[0].formatted_address lat - the number returned by google results[0].geometry.location.lat lng - the number returned by google results[0].geometry.location.lng verified - binary set by client or automatically sometimes domain - which app uses these, maybe `hrs`
The module provides the following services:
- get('/api/hrs/verify-addr/') //res is all the hrs addresses that need verification - get('/api/hrs/verify-addr/all') //res is all the hrs addresses - get('/api/hrs/verify-addr/:id') //res is a particular hrs - post('/api/hrs/verify-addr/') //201 if created a new `locations` record returns id - put('/api/hrs/verify-addr/:id') //updates with 200 or 204(no content) or 404 (not found/invalid) - delete('/api/hrs/verify-addr/:id') //deletes with 200 or 404 (not found)
</markdown>
