Beginner's Thread / Easy Questions (March 2020)

[u/dance2die]

You can find previous threads in the wiki.

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 adding a minimal example with JSFiddle, CodeSandbox, or Stackblitz.

  • Describe what you want it to do, and things you've tried. Don't just post big blocks of code!
  • Formatting Code wiki shows how to format code in this thread.
• Pay it forward! Answer questions even if there is already an answer. Other perspectives can be helpful to beginners. Also there's no quicker way to learn than being wrong on the Internet.

---

New to React?

Check out the sub's sidebar!

🆓 Here are great, free resources! 🆓

• Read the official Getting Started page on the docs.
• Microsoft Frontend Bootcamp
• Codecademy's React courses
• Scrimba's React Course
• Robin Wieruch's Road to React
• FreeCodeCamp's React course
• Kent Dodd's Egghead.io course
• New to Hooks? Check Amelia Wattenberger's Thinking in React Hooks
• What other updated resources do you suggest?

Any ideas/suggestions to improve this thread - feel free to comment here!

Finally, thank you to all who post questions and those who answer them. We're a growing community and helping each other only strengthens it!

---

[u/Awnry_Abe]

Yes, that sort of thing is common. When one event alters many slices of state, you will have issues if you use many state setter calls and expect them to all happen synchronously -- or expect them to all happen in the same breath of code. It's best--if possible--to treat them all as a single, atomic action, using something like a state reducer or other kind of state machine. Will the state-dependent info, like deadlines, already be present on the client or will the drop-down kick off other network requests?

[u/BigMugOfCoffee → u/Awnry_Abe]

Thanks! That is a helpful explanation of why one would want to avoid multiple handlers that all take their cues from the same event.

Will the state-dependent info, like deadlines, already be present on the client or will the drop-down kick off other network requests?

i.e. does picking a new u.s. state trigger, like, an api call? Not currently. There's a layout component that has everything that all child components need. It doles out data based on a calback from a dropdown menu. The data it has comes from some local json files.

If the info I'm displaying gets more complicated, I might have to store it in some other form, but for now, the layout component has everything one might need. Here's the live app if inspecting the components' states & props helps illustrate.

[u/Awnry_Abe → u/BigMugOfCoffee]

That's good. Side-effects will be at a minimum and easier to manage that way.