Question: Exposing state variables for Promise about promises HOT 2 CLOSED

Hi Zack,

The functions you've mentioned are designed for testing purposes only. Exposing promise's state and checking it explicitly is usually error prone, because it potentially leads to race conditions.

Imagine your cache access function had a completion handler instead. How would you solve your issue with the activity indicator UX then? There's couple of ways on the top of my mind:

• provide another sync function that would return either nil or a value directly if it's present in cache; if you got nil, then call the async function
• add an out argument of boolean type along with completion handler to tell if there was a cache miss
• delay showing the activity indicator and skip that if completion handler fired earlier

Similarly, you can use one of those patterns when you have an async func that returns a promise.

Hope that helps.

from promises.

Thank you for the thoughtful reply, @shoumikhin! I had also landed on the solution of providing a direct access method and using the Promise as a fallback and it's working just fine. Thanks again and have a good week.

from promises.