-
Notifications
You must be signed in to change notification settings - Fork 66
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
prepare 2.16.0 release #195
Merged
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
ensure that build happens before publish for ldclient-react
…es (#157) * [ch31880] Initial commit * Update yarn.lock * Update initLDClient.test.ts * Update package-lock.json * Update package-lock.json
# Conflicts: # packages/ldclient-js-common/typings.d.ts # packages/ldclient-react/package-lock.json
(docs 1) improve TypeScript docs and add TypeDoc build script
(docs 2) fix TypeDoc build to include types from the common package
handle security error when we're not allowed to use window.localStorage
add release script that releases all packages in js-client
…dshake remove iframe handshake code for click event UI
fix error on out-of-order delete
change TS declarations to prefer interfaces over types
# Conflicts: # packages/ldclient-react/package-lock.json
rm typedoc dependency, don't commit installation of it during release
fix programmatically reported version string
This reverts commit 34d9a0f.
update Babel, Jest, Rollup
remove unused Rollup plugins, update dependencies
use new config validation mechanism in js-sdk-common 3.x
bwoskow-ld
approved these changes
Dec 16, 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.
[2.16.0] - 2019-12-16
Added:
eventCapacity
: the maximum number of analytics events (not counting evaluation counters) that can be held at once, to prevent the SDK from consuming unexpected amounts of memory in case an application generates events unusually rapidly. In JavaScript code this would not normally be an issue, since the SDK flushes events every two seconds by default, but you may wish to increase this value if you will intentionally be generating a high volume of custom or identify events. The default value is 100.wrapperName
andwrapperVersion
: used by the React SDK, and potentially by third-party libraries, to identify a JS SDK instance that is being used with a wrapper API.Changed:
baseUri:3
orsendEvents:"no"
. For boolean properties, the SDK will still interpret the value in terms of truthiness, which was the previous behavior. For all other types, since there's no such commonly accepted way to coerce the type, it will fall back to the default setting for that property; previously, the behavior was undefined but most such mistakes would have caused the SDK to throw an exception at some later point.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!)Deprecated:
samplingInterval
configuration property was deprecated in the code in the previous minor version release, and in the changelog, but the deprecation notice was accidentally omitted from the documentation comments. It is hereby deprecated again.