* Claude update for useActionState
* Human edits
* Feedback
* Add link to form action docs
* oops
* claude feedback
* Add error handling example.
* Better useOptimistic and pending states.
* Move up "cancelling queued actions" and update form example pending state
* Ooops
* Troubleshooting updates
* Feedback
This commit fixes the wording of __Rendering__ explanation paragraph
in the "components and hooks must be pure" page, according to the suggestion
so that it's easier to understand without any confusion around effects relation.
* Revamp useOptimistic docs
* Updates from review
* Edit down a bit
* Updates from feedback
* Updates from feedback
* Updates from feedback
* fml, forgot startTransition again
* rm "prop"
* feedback from @stephan-noel
* feedback from @stephan-noel
* update note
Fixes#8097
The refactored example in the "Chains of computations" section uses
an incorrect condition that changes the game logic from the original.
The original Effect-based code advances the round after 4 gold cards:
- Increments first (0→1, 1→2, 2→3, 3→4)
- Then checks `goldCardCount > 3` (true when count is 4)
The refactored code with `goldCardCount <= 3` allows 5 gold cards:
- Checks before incrementing
- Allows counts 0, 1, 2, 3 to increment (4 values)
- Advances on the 5th card (when count is 4)
This fix changes the condition to `goldCardCount < 3`:
- Allows counts 0, 1, 2 to increment (3 values)
- Advances on the 4th card (when count is 3)
- Matches the original behavior
Verified by tracing execution logic and building the docs site locally.
Co-authored-by: PaulyBearCoding <PaulyBearCoding@users.noreply.github.com>
* fix: correct link for RedwoodJS to RedwoodSDK in documentation
* fix: update links for React Query and TanStack Start in documentation
* fix: update Vite installation command to use TypeScript template
* fix: update references from React Query to TanStack Query in documentation
