Lightning Talks Day #2 – Karol Fabjanczuk
summary
Claims that Composition API organizes medium-to-large Vue components by letting developers extract view core capabilities into standalone functions that live outside component definitions. Demonstrates using the setup option to import and return those functions so templates access grouped logic, replaces fragile mixins and HOCs, and avoids React hook traps by being evaluate only once rather than on every rerender. Recommends keeping the Options API for small components and links to a repository for concrete code.
AI-written summary · about
chapters (4)
- 0:00Start
- 1:07Benefit of Using Components Api
- 2:54Logic Wheels
- 5:05Is There a Situation in Which You Would Choose Options Api Instead of Composition Api if So Why and When
related talks
27mIntroduction into the Composition API
28mComposition API: a Quick overVue
31mIntroduction to Vue 3's Composition API
32mScalable Front End Architecture with the Composition API and Composable Functions
46mConstellations of Composables
47mVue’s Composition API: Why it’s Important
46mComposable Vue 3
36mVue 3 | Looking into the Vueture: Composition Functions