Загрузка видео...

Не удалось загрузить видео

На главную

"How can I use server components for data fetching if all my components also need hooks or onClick?" Move the interactive part into a separate component

50,631 просмотров • 1 год назад •via X (Twitter)

Комментарии: 10

Фото профиля Alfredo Lopez
Alfredo Lopez1 год назад

FYI, you don’t need a whole component just for the onClick. Client components can also be just functions, so you can import/assign the onClick from a RSC just fine.

Фото профиля Phev
Phev1 год назад

While I love the simplicity of data fetching in server components, it is very annoying to make those extra data loader wrapper components for the real (interactive) components. It would be nice if one could have server and client components defined in the same file... (where one is just a simple wrapper to load the data on the server)

Фото профиля Alex Sidorenko
Alex Sidorenko1 год назад

My mindset reversed with RSC. I mostly feel like server components are the main thing, and the client components are just wrappers of interactivity.

Фото профиля Mubashir
Mubashir1 год назад

the best strategy is to move interactive components to separate components and mark them as client components with “use client”. you can still render server components as children of those client components as long as you are not directly importing them into the file that is marked with “use client”.

Фото профиля Alexander
Alexander1 год назад

What’s the extension to get that intellisense?

Фото профиля Daniel Dunderfelt
Daniel Dunderfelt1 год назад

Or just use react-query 😌

Фото профиля Steve
Steve1 год назад

What if the children needs props from their parent?

Фото профиля Víctor
Víctor1 год назад

I love your vids!

Фото профиля Alex Sidorenko
Alex Sidorenko1 год назад

🫡

Фото профиля Summit Avenue Web Solutions
Summit Avenue Web Solutions1 год назад

I gotta ask how you’re hiding tailwind classes with little logo boi

Похожие видео