Pete Gonzalez

@akshay-madhukar The inconsistency arises because `namespace TestName` is exported but `interface TestName` is not. I actually didn't know this was even allowed in TypeScript. In most cases you would get...

*This issue belongs to a family of closely related issues. I've created [metaissue #1308](https://github.com/microsoft/web-build-tools/issues/1308) to come up with a unified fix that tackles them all together.*

@ecraig12345 That would be really great! This is definitely an important feature. Lemme think about the design and follow up...

There are some interesting design considerations for this feature. Consider [this declaration](https://github.com/microsoft/rushstack/blob/5627415032539c27e93fdddac4edf93d2c87a311/libraries/node-core-library/src/JsonFile.ts#L46): **node-core-library/src/JsonFile.ts** ```ts /** * Options for JsonFile.saveJsonFile() * * @public */ export interface IJsonFileSaveOptions extends IJsonFileStringifyOptions { /**...

Here's the JSON for the `IJsonFileSaveOptions` snippet from above: **node-core-library.api.json** ```js { "kind": "Interface", "canonicalReference": "@microsoft/node-core-library!IJsonFileSaveOptions:interface", "docComment": "/**\n * Options for JsonFile.saveJsonFile()\n *\n * @public\n */\n", "excerptTokens": [ { "kind":...

> So if it's not too difficult I'd be willing to help add this feature. @ecraig12345 Maybe we can approach it like this: I can start a PR that introduces...

@rbuckton (who might have some thoughts about these requirements)

I haven't been able to look at this yet. I'm out of office right now but will be back after Thanksgiving.

I thought about it some more. Seems like I was over-analyzing this problem. You're right that it's probably not super useful to maintain source code coordinates for each excerpt token....

Regarding the DocFX coordinates: In the interests of conciseness, we could split this information into two parts: ## Probably the same for all API items within a given NPM package...