@jecmstudios break the project down into steps. Develope an algorithm/recipe for how you will get from blank page to final result before evening writing any code. Its like building a house, you get your ideal design and you change things as you go. This helps you to avoid freestyle coding which can lead to frustration.
@ehutchllew no i got it it was just returning a promise
I mocked up the react recipe project. Please let me know some hints on how I will save the items in state and pass them using props: https://codepen.io/lalov1/pen/97756811476267a589a730dc15f881a1?editors=0010
@lalov1 you just make your child component "dumb", in the sense that both the data and the method to change that date comes from the parent, the child only purpose is to render the latter:
An example would be:
const child = ({value, onChange}) => (<div onClick={() => onChange()}>{value}</div>)
class Parent [...] {
state={value: 1}
onChange = () => this.setState({value: this.state.value +1})
render() {
return (<Child value={this.state.value} onChange={this.onChange} />)
}
}hope it helps :+1:
any one who know latex?
:star2: 2472 | @darrenfj |http://www.freecodecamp.org/darrenfj
I've fulfilled the user stories for the project.
:star2: 4792 | @masd925 |http://www.freecodecamp.org/masd925
And don't use
eval :imp:
:)
:cookie: 16 | @hansuno2 |http://www.freecodecamp.org/hansuno2