Add working with server actions blog #303
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
| } | ||
| ``` | ||
|
|
||
| 2. Server Action is then passed down to a Client Component so that it can be used with `onClick`. |
There was a problem hiding this comment.
I didn't get what we mean here
Maybe we should switch the places of the two code snippets here
There was a problem hiding this comment.
I elaborated it a little bit:
- Event handlers such as
onClickcannot be used in Server Components. Therefore we need to separate theButtonas a Client Component and pass theclapServer Action down to it.
|
|
||
| **Choosing an Approach** | ||
|
|
||
| As shown in the design with Client Components, you can also use Server Actions to fetch data. However, this is discouraged since actions only use the `POST` method. For this case, fetching the data in React Server Components and passing it down as props seems to be a better design. Moreover, this approach provides a unified simple view of the component and displays the data on first render instead of using `useEffect`. |
There was a problem hiding this comment.
can we add a source for
However, this is discouraged since actions only use the
POSTmethod
There was a problem hiding this comment.
Data Fetching and Caching in Next.js Documentation primarily uses React Server Components for data fetching. It contains no examples with Server Actions. Also Server Actions and Mutations in Next.js Documentation hints that they are intended to be used to handle form submissions and data mutations. Following statement is also from this documentation:
Behind the scenes, actions use the POST method, and only this HTTP method can invoke them.
I don't find it necessary to include these resources, do you recommend any changes?
No description provided.