Remix Single: Concurrent Mutations w/ useFetcher

Рет қаралды 32,450

2 жыл бұрын

While Remix and browsers model mutations as form navigations, `useFetcher` allows you to get the same programming model without causing a navigation. This allows apps to add pending and optimistic UI to multiple elements at the same time. Concurrent Mutations!
Learn more at remix.run

Пікірлер: 27

@josephgreve5101 Жыл бұрын

Please never stop making these. They are SO incredibly helpful.

@DEV_XO 2 жыл бұрын

Im happy to be part of this, specially with amazing people like you! Remix is so cool! ❤

@w0ble 8 ай бұрын

Ryan, you are amazing at explaining things. Never stop!

@TEMISsX Жыл бұрын

Hi, I just started using Remix after working with 'vanilla' React for 3 years now, and I like it very much, more than what I've been able to test with NextJS (which is also good too) Please keep working on this tool it's super good, full committing on it and pushing it at the office 💪

@RolandAyala Жыл бұрын

Thanks for this video -- it does a great job of showing how Remix addresses UX details that are a struggle or pita to get right in other frameworks (at least in my experience).

@MateuszWszola Жыл бұрын

Awesome video! Keep up the good work!

@afsahnasir9889 Жыл бұрын

Thanks Jim Carrey! Awesome tutorial!

@michaelneumair 2 ай бұрын

'useTransition' is now called 'useNavigation' to not conflict with React 18th 'useTransition'

@kennycrosby774 2 жыл бұрын

RIP Aunt May

@sumantturlapati1889 2 жыл бұрын

interesting. you mentioned remix fetches all the routes after the mutation to keep them in sync. is there s way to tell remix to not fetch some routes because a) one of the routes might be expensive and/or b) I know for sure there is no dependency with this mutation so I don't want that call to be made. or did I just completely misunderstand this concept?

@blade2663 2 жыл бұрын

I had the same question in mind! I think if u are using a seperate rest server u can handle cahcing on the expensive routes there

@techytimo 2 жыл бұрын

Had the same question in mind. How do you prevent remix from refetching data for some components that you think are unrelated to the mutation you made. Actually I wish you could decide what you want to be refetched after the mutation.

@liviuzachin643 2 жыл бұрын

is there a nice way to mutate form data on client/browser side before submission without using fetcher?

@anythingforweb 2 жыл бұрын

Nice videos! Is the code hosted somewhere online? Next step would be to handle multiple submit requests for adding a person. Looks similar to the delete thing, but not sure how the optimistic ui will work there.

@SyedRiyadhulKarim 7 ай бұрын

Thanks a lot....

@fabischkamau 2 жыл бұрын

Is there a way remix can keep in sync with the database in the loader function, like in a social media application where posts keeps getting added every second by different users?

@Glinkis 2 жыл бұрын

@@the_dijkstra not if you use caching properly.

@shaunpx1 Жыл бұрын

I'm currently designing architecture for an enterprise application that has a dashboard, heavy form loads and user input/data. My question is can Remix handle an application of this nature with multiple users parsing the server at 8nce? I'm trying decide between Remix and React. I l8ve the feature this framework offer but just not sure if the resources to scale would be greater with Remix? Also is there ability for client side rendering in Remix. Can I build reusable components that are rendered on the client?

@nikshirobokov Жыл бұрын

I have a Remix project. This pull ups from React most important things: JSX, useEffect and refs. No need more. The Remix makes for you: meta tags, forms, parallel data loading and much more. So. You can reuse components same as React. Or. You can develops REST API even and use this with other applications. I use this with Postgres. That's works fast. I hope, this useful for you. A new religion :)))