Skip to content
This repository has been archived by the owner on Dec 7, 2022. It is now read-only.

Gracefully handle uninitialized Launch Darkly and failed initialization #62

Open
peterbee opened this issue Apr 2, 2018 · 1 comment

Comments

@peterbee
Copy link

peterbee commented Apr 2, 2018

In order to decouple A/B tested components from <LaunchDarkly> initialization, it would be great to have <FeatureFlag> gracefully handle uninitialized LD. (It would log a warning, of course.)

Similarly, if <LaunchDarkly> does not initialize correctly (e.g., with a connection error or account error), it makes sense to log a warning and not crash the application.

@jacobmoretti
Copy link
Collaborator

Hi @peterbee, those are some good suggestions! Will definitely make an issue and prioritize this one. Thanks for the feedback 🍻

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants