Controlled and uncontrolled components

Frontend First

Το περιεχόμενο παρέχεται από το Frontend First, Sam Selikoff, and Ryan Toronto. Όλο το περιεχόμενο podcast, συμπεριλαμβανομένων των επεισοδίων, των γραφικών και των περιγραφών podcast, μεταφορτώνεται και παρέχεται απευθείας από τον Frontend First, Sam Selikoff, and Ryan Toronto ή τον συνεργάτη της πλατφόρμας podcast. Εάν πιστεύετε ότι κάποιος χρησιμοποιεί το έργο σας που προστατεύεται από πνευματικά δικαιώματα χωρίς την άδειά σας, μπορείτε να ακολουθήσετε τη διαδικασία που περιγράφεται εδώ https://el.player.fm/legal.

4M ago 47:25

MP3•Αρχική οθόνη επεισοδίου

Sam and Ryan discuss controlled and uncontrolled components in React. They talk about how uncontrolled components can be thought of as components that manage their own internal state, why you should model your complex React components after the simpler APIs of native HTML elements like inputs, why you shouldn't try to make components that are both controlled and uncontrolled, and why making a new component boundary is sometimes all you need to make your custom components behave more predictably.

Timestamps:

0:00 - Intro
1:41 - What are controlled and uncontrolled components?
6:11 - How to change a component from uncontrolled to controlled
8:48 - How do you decide when to use a controlled or uncontrolled component?
12:00 - Sortable table example and a single source of truth
15:27 - Is it always either controlled or uncontrolled?
21:09 - Color picker example and not exposing internal state
28:46 - Sortable list example with Framer Motion
39:45 - Component boundaries and wearing two hats: the library author vs. library consumer
41:43 - How do you know if you are using the wrong approach?

Links:

201 επεισόδια

#Technology #Web #Ember #Software #Development #Design #Web Development #Tech #Software Development #Frontend #Ryan Toronto #Sam Selikoff #JavaScript #Emberjs