Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ensure flags isn't set to null if bootstrapping #97

Merged
merged 1 commit into from
Jun 22, 2018

Conversation

mpcowan
Copy link
Contributor

@mpcowan mpcowan commented Jun 22, 2018

When upgrading from 1.7.0 to 2.1.2 we ran into an unexpected breaking change where although we bootstrap with localStorage, the flags would now be set to null leading to any calls to variation to throw until the client is fully ready. The behavior in the older version with the empty object allowed calls to variation to succeed before ready, but would simply use the default fallback value.

This change restores that old behavior.

When upgrading from 1.7.0 to 2.1.2 we ran into an unexpected breaking change where although we bootstrap with localStorage, the flags would now be set to `null` leading to any calls to `variation` to throw until the client is fully ready. The behavior in the older version with the empty object allowed calls to `variation` to succeed before ready, but would simply use the default fallback value.

This change restores that old behavior.
@eli-darkly
Copy link
Contributor

Good catch, thanks. There should be a release with this fix shortly.

@eli-darkly eli-darkly merged commit 04c5ce9 into launchdarkly:master Jun 22, 2018
@eli-darkly eli-darkly mentioned this pull request Jun 22, 2018
eli-darkly added a commit that referenced this pull request Sep 7, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants