We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
libraryNameOutputPrefix
If you apply this:
diff --git a/test/functional/top-level/lib/index.d.ts b/test/functional/top-level/lib/index.d.ts index 6f79e05..51223b1 100644 --- a/test/functional/top-level/lib/index.d.ts +++ b/test/functional/top-level/lib/index.d.ts @@ -13,6 +13,8 @@ function myFunction2(firstParam: string, secondParam: number): void function myFunction2(firstParam: boolean, secondParam: number): void +function myFunction3(param: foo.MyEnum): void + class MyClass { field: boolean } @@ -23,7 +25,9 @@ interface MyInterface { type MyTypeAlias = string -enum MyEnum { - FIRST, - SECOND, +namespace foo { + enum MyEnum { + FIRST, + SECOND, + } } diff --git a/test/functional/top-level/top-level.test.ts b/test/functional/top-level/top-level.test.ts index a053b86..877eac3 100644 --- a/test/functional/top-level/top-level.test.ts +++ b/test/functional/top-level/top-level.test.ts @@ -4,9 +4,13 @@ testGeneration("top-level", import.meta.url, output => ({ input: "lib/**", output, libraryName: "sandbox-top-level", + libraryNameOutputPrefix: true, granularity: "top-level", moduleNameMapper: { ".*": "sandbox-top-level" }, + namespaceStrategy: { + "foo": "package" + }, verbose: true, }))
You get /foo/MyEnum and /sandbox/top/level/.... I would expect the foo package inside the library name prefix.
/foo/MyEnum
/sandbox/top/level/...
foo
The text was updated successfully, but these errors were encountered:
packageNameMapper
No branches or pull requests
If you apply this:
You get
/foo/MyEnum
and/sandbox/top/level/...
.I would expect the
foo
package inside the library name prefix.The text was updated successfully, but these errors were encountered: