正在加载视频...

视频加载失败

加载此视频时出现问题。这可能是由于临时网络问题，或视频可能不可用。

❌ Avoid deeply nested validations that are hard to read. ✅ Instead use invariants.

George Moller

119,007 subscribers

206,841 次观看 • 1 年前 •via X (Twitter)

科学技术教育喜剧

Anya Rossi• Live Now

Private livecam show

10 条评论

George Moller 的头像

George Moller1 年前

I've been working professionally with React and JavaScript for more than 8 years and I compiled all my knowledge into 100+ infographics and 70+ video tutorials just like this one. Check them out ↓

PATRYK 的头像

PATRYK1 年前

Don’t follow this advice. It makes your code less readable, it confuses other developers and your IDE. This level of abstraction is not helping anybody. Just use early return.

Vlad Tansky 的头像

Vlad Tansky1 年前

Nice, but wouldn’t it be easier to read code with if(!condition) throw new Error(“some message”) Instead of creating abstraction?

xavi 的头像

xavi1 年前

Just use fail fast/ early return and you’ll avoid that level of abstraction.

dcodes 🦀 的头像

dcodes 🦀1 年前

just use zod

Hamilton Greene 🐷🦔 的头像

Hamilton Greene 🐷🦔1 年前

I don't like this - you're hiding important control flow inside deeply nested functions. The caller must now know that implicitly your functions use exception control flow and throw on certain conditions (also hidden). Guards (if not x return) are usually better.

Remus 的头像

Remus1 年前

Dude an "any" wrapper function? That's scares the shit out of me

Proziam 的头像

Proziam1 年前

I have to know, what are you using for the animations and graphics? Looks clean

Ndeye Fatou Diop 🚢 💻 | DEV | 🇸🇳🇫🇷 的头像

Ndeye Fatou Diop 🚢 💻 | DEV | 🇸🇳🇫🇷1 年前

💯 This makes it super hard to read the code

Seve 的头像

Seve1 年前

"early bail" or "early return" is far better terminology

相关视频

❌ Avoid difficult-to-read conditionals in React. ✅ Instead you can use ts-pattern to express complex conditions in a single, compact expression.

❌ Avoid difficult-to-read conditionals in React. ✅ Instead you can use ts-pattern to express complex conditions in a single, compact expression.

George Moller

185,781 次观看 • 2 年前

❌ Avoid multiple state variables to track status. ✅ Instead use enums.

❌ Avoid multiple state variables to track status. ✅ Instead use enums.

George Moller

152,253 次观看 • 1 年前

❌ Avoid prop-drilling your components to extend them ✅ Instead use composition

❌ Avoid prop-drilling your components to extend them ✅ Instead use composition

George Moller

50,727 次观看 • 4 个月前

❌ Don't pass props to multiple nested components in React. ✅ Instead use libraries like react-query to better handle server state.

❌ Don't pass props to multiple nested components in React. ✅ Instead use libraries like react-query to better handle server state.

George Moller

137,429 次观看 • 2 年前

❌ Avoid using useState for more complex state management ✅ Instead use useReducer ↓

❌ Avoid using useState for more complex state management ✅ Instead use useReducer ↓

George Moller

124,069 次观看 • 2 年前

❌ Avoid having components with too many props. ✅ Instead use the compound components pattern in React to embrace composition.

❌ Avoid having components with too many props. ✅ Instead use the compound components pattern in React to embrace composition.

George Moller

177,627 次观看 • 1 年前

❌ Avoid having components with too many props. ✅ Instead use the compound components pattern in React to embrace composition.

❌ Avoid having components with too many props. ✅ Instead use the compound components pattern in React to embrace composition.

George Moller

130,061 次观看 • 2 年前

❌ Avoid mixing business logic with your React components. ✅ Instead create abstraction layers that communicate with them.

❌ Avoid mixing business logic with your React components. ✅ Instead create abstraction layers that communicate with them.

George Moller

214,951 次观看 • 2 年前

❌ Avoid Provider wrapping hell in React. ✅ Instead combine all your Providers using composition.

❌ Avoid Provider wrapping hell in React. ✅ Instead combine all your Providers using composition.

George Moller

120,828 次观看 • 2 年前

❌ Avoid Provider wrapping hell in React. ✅ Instead combine all your Providers using composition.

❌ Avoid Provider wrapping hell in React. ✅ Instead combine all your Providers using composition.

George Moller

256,599 次观看 • 2 年前

❌ Avoid prop-drilling components in React ✅ Instead embrace the Provider/Consumer pattern using the Context API

❌ Avoid prop-drilling components in React ✅ Instead embrace the Provider/Consumer pattern using the Context API

George Moller

48,311 次观看 • 1 年前

❌ Don't disable ESLint warnings in useEffect ✅ Instead use useEffectEvent from React 19.2

❌ Don't disable ESLint warnings in useEffect ✅ Instead use useEffectEvent from React 19.2

George Moller

57,237 次观看 • 4 个月前

We got you covered 🤝 Can Tell us what teams to avoid ❌ Use code “Welcome” for 15% off ✅ 🛒 Order now -

We got you covered 🤝 Can Tell us what teams to avoid ❌ Use code “Welcome” for 15% off ✅ 🛒 Order now -

Mystery Champions

69,700 次观看 • 1 年前

❌ Avoid increasing time complexity by having non-normalized state variables in React . ✅ Instead normalize the structure of the state variables to reduce time complexity.

❌ Avoid increasing time complexity by having non-normalized state variables in React . ✅ Instead normalize the structure of the state variables to reduce time complexity.

George Moller

177,601 次观看 • 2 年前

🚨UPAMECANO TOTY FLASHBACK REVIEW🚨 ✅Use Tah instead🇩🇪 Final verdict: CLEAR SKIP❌

🚨UPAMECANO TOTY FLASHBACK REVIEW🚨 ✅Use Tah instead🇩🇪 Final verdict: CLEAR SKIP❌

FUT Coin Shop

29,239 次观看 • 4 个月前

❌ You 𝗺𝗶𝗴𝗵𝘁 not need a react form library ✅ Instead you can use the FormData API's

❌ You 𝗺𝗶𝗴𝗵𝘁 not need a react form library ✅ Instead you can use the FormData API's

George Moller

81,577 次观看 • 2 年前

🚨 Avoid monolithic components that combine rendering, state management, and configuration (e.g., IDs, refs) into one unit, is harder to maintain, test, and reuse. ✅ Instead split functionality into composable components and use context to share configuration and state.

🚨 Avoid monolithic components that combine rendering, state management, and configuration (e.g., IDs, refs) into one unit, is harder to maintain, test, and reuse. ✅ Instead split functionality into composable components and use context to share configuration and state.

George Moller

21,380 次观看 • 1 年前

CSS Tip! 🤙 Use custom properties to work out the nested radius of elements for you 😎 .parent { --nested-radius: calc(var(--radius) - var(--padding)); } .nested { border-radius: var(--nested-radius); } Couldn't resist making an interactive visual! CodePen.IO link below 👇

CSS Tip! 🤙 Use custom properties to work out the nested radius of elements for you 😎 .parent { --nested-radius: calc(var(--radius) - var(--padding)); } .nested { border-radius: var(--nested-radius); } Couldn't resist making an interactive visual! CodePen.IO link below 👇

jhey ʕ•ᴥ•ʔ

795,292 次观看 • 2 年前

Hard to jump through ❌ To high ✅

Hard to jump through ❌ To high ✅

Ana

136,245 次观看 • 1 个月前

⚛️ Future React tip ↓ ❌ Omitting useEffect dependencies usually leads to hard-to-find bugs. ✅ Having said that, there are use cases when you need to run an effect only when reactive parts of the useEffect changes ↓ Extract non-reactive parts with useEffectEvent()

⚛️ Future React tip ↓ ❌ Omitting useEffect dependencies usually leads to hard-to-find bugs. ✅ Having said that, there are use cases when you need to run an effect only when reactive parts of the useEffect changes ↓ Extract non-reactive parts with useEffectEvent()

George Moller

78,174 次观看 • 2 年前