When @EncryptedRoute defined controller method returns nothing (void), @nestia/fetcher had occured exception. Considering purpose of @EncryptedRoute, occuring exception from @nestia/fetcher can be considered as not a bug but a spec. However, this is so unkind to users. Even though the exception is sensible to considering its principle, users may not think such deeply. So I've changed logic of @nestia/fetcher to support void return typed @EncryptedRoute method.
Also, from now on, those libraries will always have same version number, even if no change in each module. The reason for this version integration strategy is that NestJS does it.
@nestia/fetcher@nestia/core@nestia/sdk
What's Changed
- Update typia requirement from ^4.1.14 to ^4.1.16 in /test by @dependabot in #514
- Update typia requirement from ^4.1.14 to ^4.1.16 in /packages/e2e by @dependabot in #516
- Enhance
@nestia/fetcherfor@EncryptedRouteby @samchon in #519 - Publish
@nestia/migrate@0.2.4for updating bundled files by @samchon in #520
Full Changelog: v1.5.4...v1.5.6