You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the current implementation, it is required to have endpoint prefixes and version included inside @TypedRoute and having used setGlobalPrefix or enableVersioning is impossible with nestia.
It would be much more convenient if nestia had the ability to reflect on REST endpoints in the application more accurately.
/** * This is not supported by nestia when generating * swagger docs at the moment. */app.setGlobalPrefix("api");app.enableVersioning({type: VersioningType.URI,defaultVersion: "1"});
The text was updated successfully, but these errors were encountered:
Current @nestia/sdk is looking at only controller codes.
To support that feature, @nestia/sdk needs to mount and actually run the NestJS backend server. I'd tried that way once very long time ago, but gave up it soon. It's because there had been some users that building SDK library in an environment that running the real backend server.
I think it is crazy envirionment, but of such reason, I'm very careful about this issue.
@samchon Can't you at least support the @Version decorator and the version property in @controller decorator. This would give some workaround for us to include version in the url.
In the current implementation, it is required to have endpoint prefixes and version included inside
@TypedRoute
and having usedsetGlobalPrefix
orenableVersioning
is impossible withnestia
.It would be much more convenient if
nestia
had the ability to reflect on REST endpoints in the application more accurately.The text was updated successfully, but these errors were encountered: