Skip to content
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

NextJS: transform is no longer being called in 0.41.3 #1135

Open
rburgst opened this issue Jan 31, 2025 · 5 comments
Open

NextJS: transform is no longer being called in 0.41.3 #1135

rburgst opened this issue Jan 31, 2025 · 5 comments

Comments

@rburgst
Copy link
Contributor

rburgst commented Jan 31, 2025

Describe the bug

After calling a server action which returns a new value, typically transform will be called to merge back the new state from the server.
However, lately (dont know which version, probably within the last 4 weeks), transform is not being called after the action has finished.

Your minimal, reproducible example

https://github.com/rburgst/tanstack-next-server-action

Steps to reproduce

  1. Open http://localhost:3000 with your browser to see the result.

  2. Set the age field to 12 then click Submit.

Expected behavior

the version field should be updated to 1 (from the initial value of 0).
This should happen because the transform function merges the new state from the server into the existing state.

Actual

the version field is not updated (because the transform function is not called).

How often does this bug happen?

Every time

Screenshots or Videos

No response

Platform

  • OS: Mac OSX
  • Browser: Chrome

TanStack Form adapter

None

TanStack Form version

0.41.3

TypeScript version

5.6.3

Additional context

Basically this is a slightly updated version as the vanilla next-js-server-actions example

@rburgst
Copy link
Contributor Author

rburgst commented Jan 31, 2025

ok, it only started happening in 0.41.3, in 0.41.2 everything works as expected

@rburgst rburgst changed the title NextJS: transform is no longer being called NextJS: transform is no longer being called in 0.41.3 Jan 31, 2025
@t-mart
Copy link

t-mart commented Feb 12, 2025

I see this behavior too with regression starting 0.41.3 and continuing in 0.41.4

@rburgst
Copy link
Contributor Author

rburgst commented Feb 12, 2025

Its a bit hard to see what exactly broke it but I suspect it was this change: a56d353

@rburgst
Copy link
Contributor Author

rburgst commented Feb 12, 2025

@crutchcorn can you take a look please?

@crutchcorn
Copy link
Member

Please don't tag specific maintainers.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants