Skip to content
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

[api-extractor] API Extractor 7 release branch #951

Merged
merged 140 commits into from
Nov 29, 2018
Merged

Conversation

octogonz
Copy link
Collaborator

@octogonz octogonz commented Nov 20, 2018

This is the release branch for the 7.0.0 release of API Extractor. This is a major breaking change.

Architectural changes:

  • The .api.ts review files are now created using the newer analysis engine that was used to implement the .d.ts rollups
  • The .api.json files for the documentation pipeline are also updated to use the newer analysis engine
  • The engine itself was improved and refined
  • The .api.json file format is now uses TSDoc to represent documentation, which completely replaces the MarkupElement JSON structure for representing rich text
  • The api-extractor library now provides a ApiModel API for reading/writing the .api.json file format. This provides advanced querying functionality and eliminates common mistakes.
  • The api-documenter DocItem classes have been replaced with ApiModel

New features:

  • Add support for @example tags
  • The API review file and documentation pipeline now support advanced TypeScript constructs such as overloaded functions, type aliases, merged declarations, etc.

Since this PR has too many commits for CodeFlow, please add PR comments to the temporary squashed version of this pull request: PR #952

…overhaul

# Conflicts:
#	apps/api-extractor/package.json
#	common/config/rush/shrinkwrap.yaml
(cherry picked from commit 6700652)

# Conflicts:
#	apps/api-extractor/src/api/Extractor.ts
#	apps/api-extractor/src/start.ts
(cherry picked from commit 1efb25c)

# Conflicts:
#	apps/api-extractor/src/api/Extractor.ts
…iles belonging to the current project (which may not have been built yet)

(cherry picked from commit 51fd48b)

# Conflicts:
#	apps/api-extractor/src/ExtractorContext.ts
#	apps/api-extractor/src/generators/dtsRollup/DtsRollupGenerator.ts
(cherry picked from commit c28c261)

# Conflicts:
#	apps/api-extractor/src/ExtractorContext.ts
#	apps/api-extractor/src/analyzer/PackageMetadataManager.ts
#	apps/api-extractor/src/generators/dtsRollup/DtsRollupGenerator.ts
(cherry picked from commit e97a5f0)

# Conflicts:
#	apps/api-extractor/src/api/Extractor.ts
#	apps/api-extractor/src/start.ts
[api-extractor] Support "extends" field in api-extractor.json config file

(cherry picked from commit 54eee36)

# Conflicts:
#	common/reviews/api/api-extractor.api.ts
[api-documenter] fix _getTypeNameWithDot and link implements and extends to uid

(cherry picked from commit 8d0fcab)

# Conflicts:
#	apps/api-documenter/src/yaml/YamlDocumenter.ts
…overhaul

# Conflicts:
#	apps/api-documenter/src/yaml/YamlDocumenter.ts
#	apps/api-extractor/src/ExtractorContext.ts
#	apps/api-extractor/src/analyzer/AstSymbolTable.ts
#	apps/api-extractor/src/api/Extractor.ts
#	apps/api-extractor/src/ast/AstNamespace.ts
#	apps/api-extractor/src/ast/AstStructuredType.ts
#	apps/api-extractor/src/generators/ApiJsonGenerator.ts
#	apps/api-extractor/src/generators/dtsRollup/DtsRollupGenerator.ts
#	apps/api-extractor/src/generators/dtsRollup/PackageMetadataManager.ts
#	apps/api-extractor/src/start.ts
#	apps/api-extractor/tslint.json
#	build-tests/api-extractor-test-05/etc/yaml/api-extractor-test-05/docclass1.yml
#	common/config/rush/shrinkwrap.yaml
#	common/reviews/api/api-extractor.api.ts
…we're not quite ready to dogfood the 7.0.0 beta
@octogonz
Copy link
Collaborator Author

octogonz commented Nov 29, 2018

:shipit:

Approved with PullApprove Approved with PullApprove

@octogonz octogonz merged commit 25d2894 into master Nov 29, 2018
@octogonz octogonz deleted the pgonzal/ae-overhaul branch November 29, 2018 06:58
@craigkovatch
Copy link

@octogonz is there documentation somewhere for proper syntax for @example? e.g. can I have introductory text for each example?

@octogonz
Copy link
Collaborator Author

octogonz commented Feb 5, 2019

@craigkovatch see here: microsoft/tsdoc#20 When this TSDoc issue reaches consensus, that will become the spec that we will expect API Extractor to implement.

After AE7 ships, the docs at https://api-extractor.com/pages/tsdoc/syntax/ will be updated with a complete tag reference specific to API Extractor's flavor of TSDoc.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants