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
Using function assertion to mark some properties as not optional if the function returns true but that cause typedoc to emit warning since version 0.25.3. Reverting to 0.25.2 solves the issue.
I wouldn't expect a warning to be emitted here.
Actual Behavior
Warning about duplicate declaration with different docs.
[warning] prop has multiple declarations with a comment. An arbitrary comment will be used.
[info] The comments for prop are declared at:
./src/index.ts:2
./src/index.ts:2
[info] The comments for prop are declared at:
./src/index.ts:2
./src/index.ts:2
./src/index.ts:2
./src/index.ts:2
error Command failed with exit code 3.
Steps to reproduce the bug
exportinterfaceTemplatedTypeBase{/** * Doc here */prop?: string[];}exportinterfaceOneextendsTemplatedTypeBase{}exportinterfaceTwoextendsTemplatedTypeBase{}exporttypeType=One|Two;// errorsexportfunctionisTemplateInstance(type: Type): type is Type&{prop: string[]}{returntrue;}// also errorexportfunctionisTemplateInstance2(type: Type): type is Type&Required<TemplatedTypeBase>{returntrue;}// this worksexportfunctionisTemplateInstance3(type: Type): type is Type&TemplatedTypeBase{returntrue;}
This didn't cause a warning in 0.25.2 because TypeDoc just gave up when encountering type is Type & ... and converted that type as Object. In 0.25.3, this is properly converted (but still not properly rendered, which is weird is properly rendered if I'd run the right build of the tool...)
Search terms
Union, duplicate declaration, intersection
Expected Behavior
Using function assertion to mark some properties as not optional if the function returns true but that cause typedoc to emit warning since version 0.25.3. Reverting to 0.25.2 solves the issue.
I wouldn't expect a warning to be emitted here.
Actual Behavior
Warning about duplicate declaration with different docs.
Steps to reproduce the bug
Repro PR: TypeStrong/typedoc-repros#35
Environment
The text was updated successfully, but these errors were encountered: