Merge pull request #120 from launchdarkly/2.7.2

Prepare 2.7.2 release

Author: apucacao

CHANGELOG.md

@@ -3,6 +3,12 @@
 All notable changes to the LaunchDarkly client-side JavaScript SDK will be documented in this file.
 This project adheres to [Semantic Versioning](http://semver.org).
 
+## [2.7.2] - 2018-10-17
+### Fixed:
+- Disconnecting from the stream does not close the browser tab anymore. 
+(Thanks, [Sawtaytoes](https://github.com/launchdarkly/js-client/issues/119).)
+- The configuration property `evaluationReasons` was misnamed as `evaluationExplanations` in the TypeScript definitions.
+
 ## [2.7.1] - 2018-09-27
 ### Fixed:
 - Event posts did not include the HTTP header that specifies the SDK version. They now do again. Note that the `sendLDHeaders` option does not affect this; if the header is turned off for flag requests, it should still be sent in events, since events always require a CORS preflight check anyway (and are delivered asynchronously, so the OPTIONS request does not slow down page loads).

package-lock.json

@@ -1,6 +1,6 @@
 {
   "name": "ldclient-js",
-  "version": "2.7.1",
+  "version": "2.7.2",
   "description": "LaunchDarkly SDK for JavaScript",
   "author": "LaunchDarkly <[email protected]>",
   "license": "Apache-2.0",

package.json

@@ -20,7 +20,7 @@ export default function Stream(baseUrl, environment, hash, config) {
   stream.disconnect = function() {
     clearTimeout(reconnectTimeoutReference);
     reconnectTimeoutReference = null;
-    close();
+    closeConnection();
   };
 
   stream.isConnected = function() {

src/Stream.js

@@ -131,7 +131,7 @@ declare module 'ldclient-js' {
      * variationDetail() method. Since this increases the size of network requests,
      * such information is not sent unless you request it with this option.
      */
-    evaluationExplanations?: boolean;
+    evaluationReasons?: boolean;
 
     /**
      * True (the default) if the client should make a request to LaunchDarkly for