Closed lgberro closed 11 months ago
I faced with the same problem.
export interface FileLoader {
start(url: string): void;
stop(): void;
}
export interface Downloader extends FileLoader {
startToFile(path: string): void;
}
export interface Uploader extends FileLoader {
uploadContetnt(path: string): void;
}
@startuml
interface FileLoader {
+start(url: string): void
+stop(): void
}
interface Downloader extends "src1/loader".FileLoader {
+startToFile(path: string): void
}
interface Uploader extends "src1/loader".FileLoader {
+uploadContetnt(path: string): void
}
@enduml
@bafolts, could you please release new version with this fix?
I faced with the same problem.
export interface FileLoader { start(url: string): void; stop(): void; } export interface Downloader extends FileLoader { startToFile(path: string): void; } export interface Uploader extends FileLoader { uploadContetnt(path: string): void; }
@startuml interface FileLoader { +start(url: string): void +stop(): void } interface Downloader extends "src1/loader".FileLoader { +startToFile(path: string): void } interface Uploader extends "src1/loader".FileLoader { +uploadContetnt(path: string): void } @enduml
@bafolts, could you please release new version with this fix?
Done. This is now in 3.1.3 and on npm.
If a nested folder has a file with multiple named exports the output class name gets broken.
run in root folder:
npx tplant -A -f mermaid -i '**/*.ts' -o uml.mmd
Output:
Expected:
Both Mermaid and PlantUML break because of
"FooBar/types".
Version: 3.1.2