Closed sharky98 closed 1 month ago
I was wondering if in the meantime, I can use add-swagger-target
and swagger-typescript
generators to create the swagger and types in a pre-created library project? I am not certain on how the arguments work.
:tada: This issue has been resolved in version 2.3.1 :tada:
The release is available on:
v2.3.1
Your semantic-release bot :package::rocket:
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Current Behavior
When creating a
webapi
application withskipSwaggerLib=false
, a new-types
project is created as expected. This project (I think?) is created using the@nx/js:library
generator. I have in mynx.json
configured to usevitest
as the unit test runner. However, in the dry-run I see that files such asjest.config.ts
are created, hinting that my configuration to usevitest
is not considered.Expected Behavior
The generated project uses my pre-configured
vitest
as the unit test runner.Github Repo
No response
Steps to Reproduce
nx-dotnet
configured. Make sure that anyinit
run during that setup does not install@nx/jest
.@nx/js:application
innx.json
uses"unitTestRunner": "vitest"
.nx g @nx-dotnet/core:application --name=backend --language=C# --template=webapi --dry-run
.The dry-run output shows that files for
jest
are created, when they should not be (not also we observe bug #801 in that the generated projects are not underlibs
orapps
).Nx Report
nx.json
Failure Logs
No response
Additional Information
No response