Ben Holmes

Thanks for sharing that nuance @pilcrowOnPaper. I know Astro [recently added built-in CSRF protection across requests,](https://astro.build/blog/astro-460/#experimental-support-for-csrf-protection) but I see what you mean about the payloads having different behavior. It sounds...

Thanks for that @robertvanhoesel! Good to see thorough overviews like this. I think we're pretty aligned on how we want form actions to feel. Pulling out a few pieces here:...

Appreciate the input @robertvanhoesel. I'm hearing a few pieces in your feedback: - **We can leave certain features to the community** to avoid an overly-prescriptive API. For example, generating input...

Alright, we've been iterating on form actions with a lot through feedback from core, maintainers, and the general community. It seems the thoughts that resonated most were: - **Add first-party...

Good feedback @NuroDev! I agree JSON is the best default, and we'll likely lead with that in our documentation examples. Still, the `form action` property supported in React 19 does...

Alright, thanks again for the quality input everyone. We've finally hit a point that we can draft an RFC. It includes complete docs of all expected features, and describes any...

Hey @mayank99! Appreciate the detailed input here. It sounds like you see a bit too much overhead with `defineAction()` compared to a straightforward function. A primary motivation for Zod was...

Thanks for the input @mayank99 and @okikio! Let me speak to a few bits of feedback I'm hearing: First, it sounds like there's desire to handle validation yourself without an...

Hey @cbasje! Glad you're enjoying the feature. You're right that the `base` config option should be respected from client code. I can take a look at that.

Glad you like how actions are working @robertvanhoesel! And uh... I'm very surprised this works actually. Can you give a more complete example? 😅