-
-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FEATURE] [v7] Support binding additional arguments #29
Labels
enhancement
New feature or request
Milestone
Comments
is there any update on this? |
TheEdoRan
changed the title
Actions can have multiple arguments via
[FEAT] Support Form Actions
Feb 7, 2024
.bind(null, ...args)
syntax
I'm actively working on v7 release in the |
2 tasks
TheEdoRan
changed the title
[FEAT] Support Form Actions
[FEATURE] Support Form Actions in v7
Feb 7, 2024
TheEdoRan
changed the title
[FEATURE] Support Form Actions in v7
[FEATURE] [v7] Support Form Actions
Feb 7, 2024
I include the id using hidden inputs: <input type="hidden" value="id" value={post.id} /> |
2 tasks
TheEdoRan
changed the title
[FEATURE] [v7] Support Form Actions
[FEATURE] [v7] Support additional arguments (bind, hidden inputs)
Apr 6, 2024
TheEdoRan
changed the title
[FEATURE] [v7] Support additional arguments (bind, hidden inputs)
[FEATURE] [v7] Support binding additional arguments
Apr 6, 2024
This was referenced Apr 6, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Problem
If you have a CRUD like model, you might want to provide two arguments instead of one (schema, and id of item being updated/removed). Personally, at the moment I'm doing something like this:
Today I found out that you can bind additional arguments to actions like this:
Next.js solution
https://nextjs.org/docs/app/api-reference/functions/server-actions#binding-arguments
next-safe-action
I wanted to ask others, what is their preferred way to do this.
The text was updated successfully, but these errors were encountered: