-
-
Notifications
You must be signed in to change notification settings - Fork 141
chore(developer): consolidate api-extractor usage in Developer #16135
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
Open
mcdurdin
wants to merge
2
commits into
master
Choose a base branch
from
chore/developer/14838-consolidate-api-extractor
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+193
−139
Open
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
This file contains hidden or 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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,41 @@ | ||
| # Introduction | ||
|
|
||
| These files are used by `typescript_run_api_extractor()` in typescript.inc.sh. | ||
|
|
||
| This is setup only for Developer projects at this time as outputs go into | ||
| developer/docs and developer/build; future generalization requires changing only | ||
| `$report_temp` and `$report_folder` parameters in | ||
| `typescript_run_api_extractor()`. | ||
|
|
||
| ## api-extractor.template.json | ||
|
|
||
| * Reference: https://api-extractor.com | ||
|
|
||
| api-extractor.template.json contains a template for api-extractor; these | ||
| parameters cannot be passed in to the tool, so we modify this template as needed | ||
| with the following parameters: | ||
|
|
||
| * `$keyman_root`: the `$KEYMAN_ROOT` variable, with backslash \ translated to | ||
| forward slash / | ||
| * `$index_d_ts`: the filename `index.d.ts` or the corresponding filename for the | ||
| entry point of the project | ||
| * `$project_path`: the path for the module, relative to the base of the repo | ||
| * `$report_temp`: a temporary path for output files for api-extractor | ||
| * `$report_folder`: target folder for completed api-extractor API documentation | ||
|
|
||
| ## tsdoc.template.json | ||
|
|
||
| * Reference: https://tsdoc.org/pages/packages/tsdoc-config/ | ||
|
|
||
| tsdoc.template.json is copied (unmodified) from this folder into tsdoc.json in | ||
| project folders (alongside tsconfig.json) before running api-extractor and | ||
| removed again afterwards; there is no way to specify an alternate location for | ||
| the file. | ||
|
|
||
| tsdoc.template.json includes a definition for "@since" which has been proposed | ||
| in https://github.com/microsoft/tsdoc/issues/136. | ||
|
|
||
| ## Notes | ||
|
|
||
| See also .github/workflows/api-verification.yml which does API validation of | ||
| Core for desktop platforms. |
This file contains hidden or 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
This file contains hidden or 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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,15 @@ | ||
| { | ||
| "$schema": "https://developer.microsoft.com/json-schemas/api-extractor/v7/api-extractor.schema.json", | ||
| "extends": "$keyman_root/common/tools/api-extractor/api-extractor.base.json", | ||
| "mainEntryPointFilePath": "<projectFolder>/build/src/$index_d_ts", | ||
| "docModel": { | ||
| "enabled": true, | ||
| "projectFolderUrl": "http://github.com/keymanapp/keyman/tree/master/$project_path", | ||
| "apiJsonFilePath": "$report_temp/<unscopedPackageName>.api.json" | ||
| }, | ||
| "apiReport": { | ||
| "enabled": true, | ||
| "reportFolder": "$report_folder/", | ||
| "reportTempFolder": "$report_temp/" | ||
| } | ||
| } | ||
This file contains hidden or 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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,15 @@ | ||
| { | ||
| "$schema": "https://developer.microsoft.com/json-schemas/tsdoc/v0/tsdoc.schema.json", | ||
| "extends": ["@microsoft/api-extractor/extends/tsdoc-base.json"], | ||
| "tagDefinitions": [ | ||
| { | ||
| "tagName": "@since", | ||
| "syntaxKind": "block", | ||
| "allowMultiple": false | ||
| } | ||
| ], | ||
|
|
||
| "supportForTags": { | ||
| "@since": true | ||
| } | ||
| } |
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
This file was deleted.
Oops, something went wrong.
This file contains hidden or 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
This file contains hidden or 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
This file was deleted.
Oops, something went wrong.
This file contains hidden or 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
This file contains hidden or 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
This file was deleted.
Oops, something went wrong.
This file contains hidden or 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
This file was deleted.
Oops, something went wrong.
This file contains hidden or 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
This file was deleted.
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If we would put the variables we replace in uppercase they would be easier to spot.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
True, but fairly low priority? I will leave that this time because keyman_root vs KEYMAN_ROOT 😁