Skip to content
New issue

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

fix: Allow other services with nestJs. #982

Merged
merged 1 commit into from
Dec 31, 2023
Merged

Conversation

stephenh
Copy link
Owner

Fixes #972

@stephenh stephenh merged commit 45bba3c into main Dec 31, 2023
6 checks passed
@stephenh stephenh deleted the allow-services-with-nestjs branch December 31, 2023 00:23
stephenh pushed a commit that referenced this pull request Dec 31, 2023
## [1.166.1](v1.166.0...v1.166.1) (2023-12-31)

### Bug Fixes

* Allow other services with nestJs. ([#982](#982)) ([45bba3c](45bba3c))
@stephenh
Copy link
Owner Author

🎉 This PR is included in version 1.166.1 🎉

The release is available on:

Your semantic-release bot 📦🚀

options.outputServices = [ServiceOption.DEFAULT];
}
// If using nestJs + other services, add the encode methods back
if (options.nestJs && options.outputServices.length > 0) {
options.outputEncodeMethods = true;

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This ends up running even when outputServices=false.

@Pikachews
Copy link

Also the README should be updated:

Specifically `outputEncodeMethods`, `outputJsonMethods`, and `outputClientImpl` will all be false, `lowerCaseServiceMethods` will be true and `outputServices` will be ignored.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Allow NestJS to leverage Generic definitions
2 participants