prepare 3.1.0 release #5
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
modernize dev tools
Update babel config to work in `test` without `useBuiltIns`
initial move of code from js-client-sdk-private
use spread operator instead of Object.assign
add event capacity config property
re-add deprecation comment on samplingInterval
(1) use new test helpers + misc test cleanup
(2) clean up stream testing logic
…-types clearer way to model the config option defaults/types
# Conflicts: # src/EventSender.js
add wrapper metadata options and fix custom header logic
remove image-loading logic from common code, replace it with an abstraction
apucacao
approved these changes
Dec 13, 2019
bwoskow-ld
approved these changes
Dec 13, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
[3.1.0] - 2019-12-13
Added:
wrapperNameandwrapperVersion.httpFallbackPing(to be used for the browser image mechanism - see below).Fixed:
identify, the current user (as reported bygetUser()) was being updated before the SDK had received the new flag values for that user, causing the client to be temporarily in an inconsistent state where flag evaluations would be associated with the wrong user in analytics events. Now, the current-user state will stay in sync with the flags and change only when they have finished changing. (Thanks, edvinerikson!)Removed:
js-client-sdk).