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
When the swagger explorer tries to check the controller of the nest integration and their metadata, it failes with the following error:
NestJs Repository with additional dependency: @nestjs/swagger & swagger-ui-express
I guess the origin of this error is maybe, that decorator data is not exported at build process. (but I am not sure to be honest)
Should be able to fetch metadata from the classes and reuse them.
@novu/[email protected]
7
18
Potential fix: https://stackoverflow.com/questions/58596139/nestjs-swagger-issue
Use emitDecoratorMetadata in tsconfig.json
None
The text was updated successfully, but these errors were encountered:
NV-4753 🐛 Bug Report: Incompatibility between nest-swagger-ui and @novu/framework
Sorry, something went wrong.
No branches or pull requests
📜 Description
When the swagger explorer tries to check the controller of the nest integration and their metadata, it failes with the following error:
👟 Reproduction steps
NestJs Repository with additional dependency: @nestjs/swagger & swagger-ui-express
I guess the origin of this error is maybe, that decorator data is not exported at build process. (but I am not sure to be honest)
👍 Expected behavior
Should be able to fetch metadata from the classes and reuse them.
👎 Actual Behavior with Screenshots
Novu version
@novu/[email protected]
npm version
7
node version
18
📃 Provide any additional context for the Bug.
Potential fix:
https://stackoverflow.com/questions/58596139/nestjs-swagger-issue
Use emitDecoratorMetadata in tsconfig.json
👀 Have you spent some time to check if this bug has been raised before?
🏢 Have you read the Contributing Guidelines?
Are you willing to submit PR?
None
The text was updated successfully, but these errors were encountered: