Dark Mode

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

docs: add client-side navigation pattern for use_server_future#572

Open
xsoheilalizadeh wants to merge 1 commit intoDioxusLabs:mainfrom
xsoheilalizadeh:docs/use-server-future-navigation
Open

docs: add client-side navigation pattern for use_server_future#572
xsoheilalizadeh wants to merge 1 commit intoDioxusLabs:mainfrom
xsoheilalizadeh:docs/use-server-future-navigation

Conversation

Copy link
Contributor

xsoheilalizadeh commented Oct 11, 2025

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

  • Added new "Client-Side Navigation" section after the streaming section
  • Includes comparison of non-working vs working code
  • Concise explanation of why signals are needed

This addresses a common issue developers face when building fullstack apps with Dioxus router.

Explain how to use ReadSignal props for navigation between same-component instances
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant