Setting/getting temporary state is asynchronous?

App Building
1

When running the following code we get null logged:

const val = 1;
ts.setValue(val);
console.log('ts value is');
console.log(ts.value);

Is this the expected behavior? If so, how might we accomplish the following:

  • When the page loads, we need to get the current time and save it in a var
  • This time var will be used in queries throughout the page
  • Some of those queries run immediately on pageload....but they fail sometimes, because the temporary state time var does not yet exist (as seen above, it's null for some milliseconds after setting it)
2

@aviator22

This is normal behavior. See this post: When to use Temporary State vs. local variables

2 Likes
3

Hi @aviator22!

You can try setting the initial value of your temporary state value which will make it more immediately accessible.

As to the expected behavior - this question was brought up by @bradlymathews here. To summarize: ts.setValue returns a promise which you can await and then reference the new value with ts.value if you go to the 'Advanced' tab of your query and select this option:

704×78 4.11 KB

Let me know if this works out for you!

3 Likes
4

Thanks folks, that clears it up

5

This doesn't seems like working when you import the app as module and run from parent app. Is it by design or a bug?

6

Tracking this bug here! Thanks for surfacing it :slightly_smiling_face: