On The Bike Shed, hosts Joël Quenneville and Stephanie Minn discuss development experiences and challenges at thoughtbot with Ruby, Rails, JavaScript, and whatever else is drawing their attention, admiration, or ire this week.
…
continue reading
Content provided by The Enjoy the Vue Team. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by The Enjoy the Vue Team or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://podcastplayer.com/legal.
Player FM - Podcast App
Go offline with the Player FM app!
Go offline with the Player FM app!
Episode 48: New in Vue 3: The Composition API
MP3•Episode home
Manage episode 282659759 series 2610000
Content provided by The Enjoy the Vue Team. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by The Enjoy the Vue Team or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://podcastplayer.com/legal.
Key Points From This Episode:
- Introducing today’s panel, Ari and Tessa.
- We kick off the episode by looking at composition API.
- Side effects and collisions one can expect when using Composition API.
- How composition API can solve mixin problems.
- Hear about the process behind conflating data with filtering.
- Ari tells us about a foot gun, and why they ought to be avoided.
- The best ways for users to start learning composition API.
- Find out what is exposed by the composition API.
- Parting thoughts from our panel.
- Hear the team’s picks for this week!
Tweetables:
- “Composition API is the ability to share features across different components in a way that's modular, but in a way that also, you can maintain and track.” — @enjoythevuecast [0:03:23]
- “In components when you have so many features that it's hard to tell what's talking to what anymore, this is really where people start to want to break things apart. This is where composition API can shine.” — @enjoythevuecast [0:07:28]
- “Just because you can use a tool, it doesn't mean you should.” — @enjoythevuecast [0:22:26]
Links Mentioned in Today’s Episode:
93 episodes
MP3•Episode home
Manage episode 282659759 series 2610000
Content provided by The Enjoy the Vue Team. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by The Enjoy the Vue Team or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://podcastplayer.com/legal.
Key Points From This Episode:
- Introducing today’s panel, Ari and Tessa.
- We kick off the episode by looking at composition API.
- Side effects and collisions one can expect when using Composition API.
- How composition API can solve mixin problems.
- Hear about the process behind conflating data with filtering.
- Ari tells us about a foot gun, and why they ought to be avoided.
- The best ways for users to start learning composition API.
- Find out what is exposed by the composition API.
- Parting thoughts from our panel.
- Hear the team’s picks for this week!
Tweetables:
- “Composition API is the ability to share features across different components in a way that's modular, but in a way that also, you can maintain and track.” — @enjoythevuecast [0:03:23]
- “In components when you have so many features that it's hard to tell what's talking to what anymore, this is really where people start to want to break things apart. This is where composition API can shine.” — @enjoythevuecast [0:07:28]
- “Just because you can use a tool, it doesn't mean you should.” — @enjoythevuecast [0:22:26]
Links Mentioned in Today’s Episode:
93 episodes
All episodes
×Welcome to Player FM!
Player FM is scanning the web for high-quality podcasts for you to enjoy right now. It's the best podcast app and works on Android, iPhone, and the web. Signup to sync subscriptions across devices.