MDN has a very good page on async (and await ) . Having read them the MDN page plus a bunch of other tutorials, here are my key takeaways: In general: async and await are just a nicer syntax for working with promises. So learn promises. Understand promises. And then use async and await to make your promise-using code look nicer. About async : Putting async in front of a function definition allows you to use await inside that function. Putting async in front of a function definition also wraps the function's return value in a promise, if the return value wasn't a promise already. So if my function gets data via a promise and then extracts and transforms the data before returning it, I can just return my transformed data and let async magically re-promise-ify the data for me. :-) About await : await lets me use functions that return promises, but write code that looks synchronous, i.e.the code looks as if the function that returns a promise was an old fa...
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. ---------------------...
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