react-launch-darkly icon indicating copy to clipboard operation
react-launch-darkly copied to clipboard

Gracefully handle uninitialized Launch Darkly and failed initialization

Open peterbee opened this issue 6 years ago • 1 comments

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.

peterbee avatar Apr 02 '18 20:04 peterbee

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

jacobmoretti avatar Apr 03 '18 06:04 jacobmoretti