You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I know it's pretty early in experimentation, but I'm working to kludge together something that works for multiple entrypoints because the libraries we use often do have multiple entry points in practice. I'll document my experiences with that somewhere else, but this ticket is about one small discrepancy I've noticed while working through this.
Summary
I know it's pretty early in experimentation, but I'm working to kludge together something that works for multiple entrypoints because the libraries we use often do have multiple entry points in practice. I'll document my experiences with that somewhere else, but this ticket is about one small discrepancy I've noticed while working through this.
EntryPoint
s should have an import path which doesn't include the leading/
: https://github.com/microsoft/tsdoc/blob/main/tsdoc/src/beta/DeclarationReference.ts#L331-L333{@link @mscharley/my-package/import-path#MyClass}
have an import path of/import-path
which breaks this check here: https://github.com/microsoft/rushstack/blob/main/libraries/api-extractor-model/src/model/ModelReferenceResolver.ts#L77-L83These two pieces of code seem in conflict, but I don't know which is correct.
Repro steps
I can post a repro project if you want, but the only repro I have at the moment is a private project and this seems a pretty straightforward issue.
Details
The patch I'm running at the moment which seems to clear up all the issues I've run into so far is:
This generates links correctly in the documentation that is generated.
More than happy to format this as a proper PR but I don't have the context for the project to know if this is the proper fix or not.
Standard questions
Please answer these questions to help us investigate your issue more quickly:
@microsoft/api-extractor-model
version?@microsoft/tsdoc
version?node -v
)?The text was updated successfully, but these errors were encountered: