-
-
Notifications
You must be signed in to change notification settings - Fork 129
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
docs: New blog about Progressive Forms #1195
base: main
Are you sure you want to change the base?
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. |
|
||
## What does this look like? | ||
|
||
So before React 19 and before we had waku server actions, a very basic form might look like this: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So before React 19 and before we had waku server actions, a very basic form might look like this: | |
So before React 19 and before we had Waku server actions, a very basic form might look like this: |
|
||
## Introducing progressive forms with Waku Server actions | ||
|
||
In this example, it can be pure RSC built. There is no client JS needed. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To clarify, the primary goal isn't to support non-JS browser.
Even if you enable JS, the progressive form works while loading JS code and before hydration finishes.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
reworded this part... let me know what you think :)
Putting up my first draft :) -- I'll need feedback on this.
Some things I was unsure of: