Improvement Ideas based on 09.2023

[csalv22]

Improvements next time:

• [x] Add slide that explains useEffect and how it works (with a reasonable sample stolen from react.dev)
• [x] Wrap all first component Exercises to one
• [ ] ~Make the project start from github clone, so the branches are available~
• [x] Combine all React Router theory input into one and make one exercise
• [x] Remove exercises for the Testing (but keep the explanation)
• [ ] Add a Slide with to visualize how a virtual DOM & render cycle works , upon mounting/onmounting etc. Maybe reuse things from the react docs?

[radaced]

• [ ] mention somewhere to update their vs-code instances resp. generally prefer using vs-code for participants maybe?
• [x] generate DTO's or provide needed ones from PokeAPI
• [x] remove limit param in post request in tanstack query mutation examples
• [x] maybe include comparison link between different query-libraries (https://tanstack.com/query/latest/docs/react/comparison)
• [ ] stretch goal custom hook exercise: what are wanted or unwanted side effects of using e.g. useParams hook in your custom hook?
• [x] row-based highlighting on step by step useContext example

[felixmokross]

• [ ] First Components: Explain better that the component function is called on every render (esp. difference to other frameworks like Solid), and how the render cycle works
• [x] First Components / Testing: Participants are confused that we have to change the Vite config to use the import { defineConfig } from 'vitest/config' – is there a less confusing way to do it?
• [x] First Components / Testing / TDD: de-emphasize this (I wouldn't recommend this personally as a standard practice)
• [x] First Components / Testing / Refactoring: de-emphasize (wouldn't do it personally like this, not relevant for a React course)
• [x] First Components / Testing / Exercise / Stretch Goal: it's fine as a stretch goal to give more advanced participants something to dive into. But I think the example is not good, for such a simple component it doesn't make a lot of sense to use parameterized testing.
• [x] Forms: Format React Hook Form examples nicer
• [x] Side Effects: Duplication of previous points on slide "Cleanup is necessary for"
• [x] Side Effects: Better introduce other hooks like 'useCallback' and 'useMemo'
• [x] Side Effects: Give outlook on "React Forget" (the upcoming React compiler to get rid of useCallback/useMemo)
• [x] Side Effects / Custom Hook Exercise: Discuss stretch goal with uriBuilder

[felixmokross]

Remove exercises for the Testing (but keep the explanation)

I merged the exercises in First Components now and made the testing a stretch goal (just simple testing, no parameterized testing).