@microsoft/api-extractor - npm Package Compare versions

Comparing version 1.1.19 to 2.0.0

CHANGELOG.json

		@@ -5,2 +5,14 @@ {
		{
		"version": "2.0.0",
		"tag": "@microsoft/api-extractor_v2.0.0",
		"date": "Mon, 20 Mar 2017 21:52:20 GMT",
		"comments": {
		"major": [
		{
		"comment": "Fixing whitespace, also a variable that was shadowing another variable."
		}
		]
		}
		},
		{
		"version": "1.1.19",
		@@ -7,0 +19,0 @@ "tag": "@microsoft/api-extractor_v1.1.19",

CHANGELOG.md

		# Change Log - @microsoft/api-extractor

		This log was last generated on Mon, 20 Mar 2017 04:20:13 GMT and should not be manually modified.
		This log was last generated on Mon, 20 Mar 2017 21:52:20 GMT and should not be manually modified.

		## 2.0.0
		Mon, 20 Mar 2017 21:52:20 GMT

		### Breaking changes

		- Fixing whitespace, also a variable that was shadowing another variable.

		## 1.1.19
		@@ -6,0 +13,0 @@ Mon, 20 Mar 2017 04:20:13 GMT

lib/DocElementParser.js

		@@ -203,8 +203,8 @@ "use strict";
		}
		// We are going to copy the resolvedApiItem's documentation
		// We are going to copy the resolvedApiItem's documentation
		// We must make sure it's documentation can be completed,
		// if we cannot, an error will be reported viathe documentation error handler.
		// This will only be the case our resolvedApiItem was created from a local
		// if we cannot, an error will be reported viathe documentation error handler.
		// This will only be the case our resolvedApiItem was created from a local
		// ApiItem. Resolutions from JSON will have an undefined 'apiItem' property.
		// Example: a circular reference will report an error.
		// Example: a circular reference will report an error.
		if (resolvedApiItem.apiItem) {
		@@ -211,0 +211,0 @@ resolvedApiItem.apiItem.completeInitialization();

lib/DocItemLoader.js

		@@ -33,7 +33,7 @@ "use strict";
		DocItemLoader.prototype.resolve = function (apiDefinitionRef, apiPackage, reportError) {
		// If there is a packageName then there must be a scopeName, and they
		// If there is a packageName then there must be a scopeName, and they
		// both must match the current scope and package we are in.
		// We can take advantage of '&&' being evaluated left to right.
		if (!apiDefinitionRef.packageName && !apiDefinitionRef.scopeName) {
		// Resolution for local references
		// Resolution for local references
		return this.resolveLocalReferences(apiDefinitionRef, apiPackage, reportError);
		@@ -92,3 +92,3 @@ }
		}
		// found JSON package, now ensure export name is there
		// found JSON package, now ensure export name is there
		// hasOwnProperty() not needed for JJU objects
		@@ -95,0 +95,0 @@ if (!(apiDefinitionRef.exportName in docPackage.exports)) {

lib/generators/ApiFileGenerator.js

		@@ -75,3 +75,3 @@ "use strict";
		// Type literals don't have normal JSDoc. Write only the warnings,
		// and put them after the '{' since the declaration is nested.
		// and put them after the '{' since the declaration is nested.
		_this._writeWarnings(apiStructuredType);
		@@ -78,0 +78,0 @@ }

package.json

		{
		"name": "@microsoft/api-extractor",
		"version": "1.1.19",
		"version": "2.0.0",
		"description": "Validatation, documentation, and auditing for the exported API of a TypeScript package",
		@@ -28,4 +28,5 @@ "main": "lib/index.js",
		"jju": "~1.3.0",
		"typescript": ">=2.2.1-0 <3.0.0-0",
		"z-schema": "~3.17.0"
		}
		}

lib/ApiDefinitionReference.js.map