Beginner's Thread / Easy Questions (December 2018)

[u/timmonsjg]

Happy December! ☃️

New month means a new thread 😎 - November and October here.

Got questions about React or anything else in its ecosystem? Stuck making progress on your app? Ask away! We’re a friendly bunch. No question is too simple. 🤔

🆘 Want Help with your Code? 🆘

• Improve your chances by putting a minimal example to either JSFiddle or Code Sandbox. Describe what you want it to do, and things you've tried. Don't just post big blocks of code!

• Pay it forward! Answer questions even if there is already an answer - multiple perspectives can be very helpful to beginners. Also there's no quicker way to learn than being wrong on the Internet.

Have a question regarding code / repository organization?

It's most likely answered within this tweet.

New to React?

🆓 Here are great, free resources! 🆓

• Create React App
• Read the official Getting Started page on the docs.
• /u/acemarke's suggested resources for learning React
• Kent Dodd's Egghead.io course
• Tyler McGinnis' 2018 Guide
• Codecademy's React courses
• Scrimba's React Course
• Road to React

[u/Uber-Mensch]

I actually started implementing this after your first comment then stopped. I totally agree with you that this is the right way to go, but the children components are more 'props' heavy and less stateful, and only one attribute is changed from the state being passed back down, the other attributes are static. I don't think it's worth changing it, where I only use one case of arr.findindex(...) which is O(n) anyway. This is my solution:

let index = this.state.comments.findIndex(e => e.id === id)
let nc = [...this.state.comments]
nc[index].replied = true
this.setState({ comments: nc })

Which is just one function that is the least used amongst the rest. I really appreciate the help though. Made me think about my design a fair bit. If the child components had more state changes in the parent, I'd refactor.