You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello! First, I'll give some context on the use case here. I am implementing a method that waits for the LaunchDarkly client to be fully initialized before the first feature flag evaluation to ensure that the first evaluation doesn't fall back to the default value.
I attempted to use the DataSourceProvider.WaitFor() method to achieve this; however, after testing, I saw that this method waits for the Valid state and not the Initialized state. So, when we call the client for the first time, it is still not initialized. I'm not sure of what the internals are on how these two states are different, but I believe it's not the expected behavior for this WaitFor() method to return when the client is not in a fully ready state. The desired behavior, as I see it, would be for WaitFor() to wait for the full initialization state and not the validity state, or at the least have an option to do so.
Thank you so much in advance!
The text was updated successfully, but these errors were encountered:
HI @IsabellaCapriottiUIPath , could you provide a snippet of your code? Also, which version of the SDK are you using? This may be better handled by opening a support ticket. If you do choose to open a ticket, I highly recommend including code snippets of how you're initializing the client.
Hello! First, I'll give some context on the use case here. I am implementing a method that waits for the LaunchDarkly client to be fully initialized before the first feature flag evaluation to ensure that the first evaluation doesn't fall back to the default value.
I attempted to use the DataSourceProvider.WaitFor() method to achieve this; however, after testing, I saw that this method waits for the Valid state and not the Initialized state. So, when we call the client for the first time, it is still not initialized. I'm not sure of what the internals are on how these two states are different, but I believe it's not the expected behavior for this WaitFor() method to return when the client is not in a fully ready state. The desired behavior, as I see it, would be for WaitFor() to wait for the full initialization state and not the validity state, or at the least have an option to do so.
Thank you so much in advance!
The text was updated successfully, but these errors were encountered: