Suppose you have weird taste and you absolutely want:
- your visual selection to always have a green background and black foreground,
- your active statusline to always have a white background and red foreground,
- your very own deep blue background.
First couple things I thought about when migrating after reading the docs
So migrating my existing app wasn't as troublesome as I originally thought. First thing I did was take a look at my router and routes
and figure try to make a mental model of all the files where I had nested routes in the existing app because those components/containers will contain {this.props.children}. So I need to replace those with the nested <Match /> components.
So just to give an example:
<Router history={history}>
<Route path="/" component={App}>| { | |
| "parser": "babel-eslint", | |
| "env": { | |
| "es6": true, | |
| "mocha": true, | |
| "node": true | |
| }, | |
| "ecmaFeatures": { | |
| "blockBindings": true, | |
| "forOf": true, |
#A brief intro into Stateless functions#
So stateless functions are new in React 0.14 which are quite interesting. They look a bit like this.
const Test = ({name, amount}) => {
return <div className="test">{name} has £{amount}</div>;
};
ReactDOM.render(<Test name="ben" amount="-2000" />) // <div className="test">ben has £-200</div> 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')react + redux + RR
It uses https://gist.github.com/iNikNik/3c1b870f63dc0de67c38 for stores and actions.
1) create redux
const redux = createRedux(state);2) get requireAccess func => bindCheckAuth to redux
| { | |
| "env": { | |
| "browser": true, | |
| "node": true, | |
| "es6": true | |
| }, | |
| "plugins": ["react"], | |
| "ecmaFeatures": { |
Currently considering https://github.com/webdriverio/webdrivercss
Core Goals:
- Can test in up-to-date versions of all major browsers
- Can test on up-to-date versions of all major OSes
- Can test in IE9 (because Bootstrap v4 will support IE9+)
- Don't want to have to setup/maintain our own cluster of VMs running all the necessary OSes (and all the versions of Windows)
- Workflow for management of reference/baseline/norm screenshots