prepare 2.16.0 release #16
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
* applying the readme template * clarifying text * wrapper => sdk * clarify relationship to js sdk * re-ordered the changelog header
* reinstate 2.12.5 and 2.13.0 * lint errors * adding a missing file
…vate into yus/ch43034/make-react-sdk-support-bootstrapping-natively
* reinstate 2.12.5 and 2.13.0 * lint errors * adding a missing file * doc comments * cleanup * fix lint errors * fix lint errors * fix lint errors * undo a commit * undo a commit * add typedoc build (#6) * add typedoc build * add makefile * exclude test code * doc comment fixes * more code doc cleanup * minor doc update
…ded more information comparing asyncCreateLDProvider and withLDProvider to typedoc.
…vate into yus/ch43034/make-react-sdk-support-bootstrapping-natively
…pport-bootstrapping-natively [ch43034] React sdk support for bootstrapping natively
# Conflicts: # CHANGELOG.md # package-lock.json # package.json
…nt-sdk-urls Update homepage and git repo url to point to the new react sdk page
* update js-sdk-common + misc build improvements * update dependency * fix typedoc build logic
…ate hook when updating flags.
…rors-warnings-upgrades [ch55739] Fixed example errors, warnings and upgrade major packages.
…s-and-bootstrapping-bugs [ch55738] Fix async provider initialisation bug
…pdate-common-sdk use latest JS SDK release, add wrapper properties
yusinto
approved these changes
Dec 16, 2019
bwoskow-ld
approved these changes
Dec 17, 2019
LaunchDarklyCI
pushed a commit
that referenced
this pull request
Dec 18, 2019
* export camel-case util * lint errors
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.wrapperNameandwrapperVersion: used by the React SDK to identify a JS SDK instance that is being used with a wrapper API.Changed:
baseUri:3orsendEvents:"no"(normally not possible in TypeScript, but could happen if an arbitrary object is cast toLDOptions). 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:
samplingIntervalconfiguration 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.