Skip to content
New issue

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

早报@2019-03-19 #76

Open
whatwewant opened this issue Mar 18, 2019 · 0 comments
Open

早报@2019-03-19 #76

whatwewant opened this issue Mar 18, 2019 · 0 comments
Labels

Comments

@whatwewant
Copy link
Owner

Writing Resilient Components — Overreacted

  • 1 Don’t stop the data flow. Props and state can change, and components should handle those changes whenever they happen.
  • 2 Always be ready to render. A component shouldn’t break because it’s rendered more or less often.
  • 3 No component is a singleton. Even if a component is rendered just once, your design will improve if rendering twice doesn’t break it.
  • 4 Keep the local state isolated. Think about which state is local to a particular UI representation — and don’t hoist that state higher than necessary
  • 5 use hooks
  • tags: React,Hooks,Dan Abramov

高级前端基础-JavaScript抽象语法树AST - 掘金

  • tags: AST,抽象语法树,TypeScript
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant