Skip to content
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

use_server_future does not caching server function calls correctly #2264

Closed
3 tasks
ealmloff opened this issue Apr 6, 2024 · 0 comments · Fixed by #2365
Closed
3 tasks

use_server_future does not caching server function calls correctly #2264

ealmloff opened this issue Apr 6, 2024 · 0 comments · Fixed by #2365
Labels
bug Something isn't working fullstack related to the fullstack crate performance

Comments

@ealmloff
Copy link
Member

ealmloff commented Apr 6, 2024

Problem

#2236 polls the use_server_future again on the client which causes server functions called directly in the future to be fetched again.

Steps To Reproduce

Steps to reproduce the behavior:

  • run the axum-hello-world example
  • view the network tab
  • observe the server function API call

Expected behavior

The server function return should be cached on the server and sent to the client serialized into the HTML

Screenshots

Screenshot 2024-04-06 at 12 02 24 PM

Environment:

  • Dioxus version: master
  • Rust version: nightly
  • OS info: MacOS
  • App platform: fullstack

Questionnaire

  • I'm interested in fixing this myself but don't know where to start
  • I would like to fix and I have a solution
  • I don't have time to fix this right now, but maybe later
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working fullstack related to the fullstack crate performance
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant