Chaining multiple dmx-value elements behavior?

1

I have several related dmx-value statements at the top of my content page. They build path statements to help shorten code later in the page. I've made the incorrect assumption in the past that my dynamic page elements would execute in series (I'm old enough to have learned web development when this was true...old habits). So as I'm doing code reviews today, I noticed I built several variables with this assumption on a page.

While the page works, I do see some unusual entries in the Network section of Dev Tools I'm trying to resolve.

So the question is, how do you properly use multiple dmx-value statements when the next statement builds on the previous one?

Here's a code example:

<dmx-value id="varCustPortal" dmx-bind:value="'/videos/'+scgetCustDetails.data.queryCustDetails.customer_portal+'/'"></dmx-value>
<dmx-value id="varLatestVideo" dmx-bind:value="varCustPortal.value+scLatestVideo.data.querygetlatestvideo[0].filename"></dmx-value>
2

Because dmx-bind is reactive, whenever a variable used in an expression changes the value is recomputed.

You mention you see some unusual entries in the network section of the dev tools, it would be interesting to see the relevant code to see how it's being triggered and what could be enhanced to only trigger once the previous variable(s) have the adequate data.

But in regards to your intent, I believe in the past people would've used a 10 ms delay in a Dynamic Event "On Success" of scgetCustDetails to trigger the next Server Connect load - this would (empirically) ensure all previous dmx-values would be recomputed, after the primary Server Connect scgetCustDetails was loaded.

Disclaimer: I'm not an advanced user in the front-end