Unexpected Server Round Trips

[braje]

I have been loving using leptos! Thank you for the wonderful project! I am having some difficulties that probably amount to me not understanding how things work. I have read the manual multiple times and haven't been able to figure it out. This post may be long, but bear with me.

I am trying to build an application which reactively handles async requests to a server. In short, I have some routes defined something like:

<ParentRoute path=/foos/:id view=xx>
  <Route path="bars" view = yy/>
  <Route path="" view= "an A anchor that calls bars" />
</ParentRoute>

The idea is that I have some foo objects that have some nested bars in them. I want to be able to view the detail view for the foo without loading the nested bars. So, my xx view uses the use_params function to capture the foo_id, wrapped in a Memo. I then have a resource that triggers on changes to that foo_id and calls a server function defined in another file. As a sibling of the "detailed foo view" is an "outlet" so that the yy view can be plugged in if the user clicks the anchor provided by the blank path.

The problem I am seeing is that clicking on this anchor rerenders the entire page even though the url changes from, say, "/foos/1" to "/foos/1/bars". My expectation is that just the "yy" view would be filled in without re-querying the server function that gives the detailed foo view.

I am using an actix backend. It is pretty clear to me that the server function is never called in "client mode" where a request is made back to the server to gather additional data. I must be doing something wrong.

Some things I pretty clearly don't understand:

• Routes are filled into the actix server by handing the "App" which contains the routes to a function I don't remember the name of because I don't have my work computer with me. :) However, the docs say that server functions are part of your public api, but it isn't clear to me that those are actually being provided anywhere. How would the above function know to look into my separate rust file that I currently implement my server functions in. I am pretty clearly missing something here.
• There seems to be a function called spawn_local which is supposed to make these client requests. I am currently using Resources in my components to make the server-side calls. I tried to refactor part to use spawn_local and the behavior didn't seem to change (i.e., the re-render the whole page when only a part of the url changes). I guess I am not clear on if Resources are supposed to allow this async client-to-server call or if they only happen upon rendering server side.

If I need to create a minimized example to show the behavior I am seeing, I am sure I can do that. I just suspect I am completely misunderstanding something that could be cleared up without that...

Thank you!

[gbj]

The problem I am seeing is that clicking on this anchor rerenders the entire page

This sounds like the actual issue to me. The rest of what you're doing sounds fine. If you are using the router, you are not using islands, and the page has hydrated correctly, click an <a> should not do a full server round-trip.

There are no other warnings or errors in the browser console?

If not, then some more code to look at, or a minimal example, would be helpful.

[braje]

Thank you for the quick response! After starting to put together a minimal example, I found that I had forgotten to put in the Hydration tag in my html, so hydration was never happening! That mostly fixes things, except I am currently getting some duplication in my page, which I hope I will be able to debug myself.