I think I understand the pieces now... React Functional Components: Are the preferred kind of component we write in React-Redux Are functions that take a "props" object Are the preferred way to output visual stuff and wire up events The Redux Store: Has all the state which we can display Has the dispatch(action) method, which is the only way to change state Your Mission (should you choose to accept it): Use the state and the dispactch(action) function Create props which are data values needed by the functional component Create props which are event handlers that call dispatch(action) The Locations: mapStateToProps : Here you get the state and return props which are just data mapDispatchToProps : Here you get the dispatch function and return props which call it And then React-Redux's "connect" function magically combines the mapping functions and your functional component into a new component which you elsewhere. ---------------------...
This is the story of Jerry JavaSript's Automated Slow Doughnut Shop. One day, I wanted a doughnut. So I rode my bike to the automated slow doughnut shop, where they have a slow doughnut machine. You put in a dollar. And then the machine mixes batter, heats the fat, drops the batter into the fat, lifts it out on a linked metal conveyor belt, dusts it with sugar, and drops it into your waiting hands. Once I get my doughnut, I can eat it in the usual manner. But from the time I put in my dollar until the time I receive my doughnut, I am blocked. Fortunately, the slow doughnut machine has a slot labeled, "Insert callback here". This is great. I code up a function eatDoughnut(doughnut) . I can reference my teeth, esophagus, stomach, and so on, because they are mine and I know all about them. And then I slip my eatDoughnut(doughnut) function into the slot and get on my bike and ride to the office while the slow doughnut machine is still mixing...
Just Enough to Get Started with Git and Github Given a project started locally outside of Git. Move it to git and github: https://help.github.com/articles/adding-an-existing-project-to-github-using-the-command-line/ Workflow: git status git add foo git commit -m " fooooooooooo" git push origin master Next, a One-Person Workflow with Branching #Start with a project in a happy, committed state #Master is our main/production branch #Create a branch to work on a new feature #git checkout -b <new_branch> <start_point> git checkout -b new-feature master #The above is the same as # git branch new-feature # git checkout new-feature #See all the branches git branch #Push the new branch to Github. After this, "git push" will update everything. git push --set-upstream origin new-feature <Do stuff & commit.> #Store your commit saf...
Comments
Post a Comment