docs: add client-side navigation pattern for use_server_future #572
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Adds documentation for using ReadSignal props with use_server_future when navigating between instances of the same component.
Problem
When navigating between same-component instances (e.g., Product A → Product B), use_server_future with plain props doesn't update content because the closure doesn't detect the prop change.
Solution
Shows the pattern of using ReadSignal props instead of plain props to enable reactivity.
Changes
This addresses a common issue developers face when building fullstack apps with Dioxus router.