We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Don’t stop the data flow
Always be ready to render
No component is a singleton
Keep the local state isolated
use hooks
自从很早以前用了jekyll, 已经很久没管静态博客了,虽然见过不少,但是基本没使用,作为Reacter, 是时候试试了
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Writing Resilient Components — Overreacted
Don’t stop the data flow
. Props and state can change, and components should handle those changes whenever they happen.Always be ready to render
. A component shouldn’t break because it’s rendered more or less often.No component is a singleton
. Even if a component is rendered just once, your design will improve if rendering twice doesn’t break it.Keep the local state isolated
. Think about which state is local to a particular UI representation — and don’t hoist that state higher than necessaryuse hooks
高级前端基础-JavaScript抽象语法树AST - 掘金
Migrating from Medium to Gatsby | no.lol - A blog by Lauren Tan
自从很早以前用了jekyll, 已经很久没管静态博客了,虽然见过不少,但是基本没使用,作为Reacter, 是时候试试了
Setting performance budgets with webpack | web.dev
2019年大前端技术趋势深度解读 - 狼叔 | 前端之巅
sindresorhus/type-fest: A collection of essential TypeScript types
深入理解 TypeScript | 深入理解 TypeScript
The text was updated successfully, but these errors were encountered: