Skip to content
This repository has been archived by the owner on May 30, 2024. It is now read-only.

5.7.2 #142

Merged
merged 179 commits into from
Feb 22, 2019
Merged

5.7.2 #142

merged 179 commits into from
Feb 22, 2019

Conversation

eli-darkly
Copy link
Contributor

[5.7.2] - 2019-02-22

Fixed:

  • Calling identify() or track() with no user object, or with a user that has no key, will now cause the SDK to log a warning (as the other SDKs do). The SDK no longer sends an analytics event in this case, since LaunchDarkly would discard the event as invalid anyway. Also, previously, calling identify() with no user object would throw an exception.
  • FileDataSource, in auto-update mode, could sometimes reload files more than once when they were only modified once (due to a known issue with Node's fs.watch). This should no longer happen. (#138)
  • Fixed dependency vulnerabilities flagged by npm audit. These were all for test-only dependencies, so would not affect production code.
  • Previously, CI tests were only running on Linux. We have added a CI test suite that runs on Windows, using the latest stable version of Node.
  • A supported user property, privateAttributeNames, was not usable from TypeScript because it was omitted from the TypeScript declarations.
  • In TypeScript, asynchronous methods that can either take a callback or return a Promise were not usable in the Promise style, because the return types were declared incorrectly. (#141)
  • Some TypeScript declarations that used type now use interface instead, except for LDFlagValue which is a type alias. This should not affect regular usage of the SDK in TypeScript, but it is easier to extend an interface than a type if desired.

Arnold Trakhtenberg and others added 30 commits July 11, 2018 10:55
…hods-to-typescript-definitions

[ch20232] Add flag util methods to typescript definitions
The following vulnerabilities are fixed with an upgrade:
- https://snyk.io/vuln/npm:cryptiles:20180710
[Snyk] Fix for 1 vulnerable dependencies
remove npm dependency on "crypto", use built-in version instead
treat HTTP 400 as a recoverable error
update doc comment for new waitForInitialization behavior
fix waitForInitialization to always resolve with a value
Update LDFeatureStore type definition for versioned data kind
add new version of allFlags() that captures more metadata
# Conflicts:
#	package-lock.json
bump jest version to stop vulnerability warning
fix track() and identify() to reject missing/keyless user
# Conflicts:
#	package-lock.json
stop file data source from doing unnecessary reloads
many TS doc fixes and TypeDoc build script
@eli-darkly eli-darkly merged commit e626445 into master Feb 22, 2019
@eli-darkly eli-darkly deleted the 5.7.2 branch February 22, 2019 23:59
LaunchDarklyCI pushed a commit that referenced this pull request Aug 20, 2019
update doc comment for track() with metricValue
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants