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
When calling the app.setGlobalPrefix(...) function in nestia.config.ts, it appears that the paths mentioned in the "exclude" option are also getting the global prefix (see example below). The correct behavior is that such paths should be excluded from the global prefix. When the SDK generates the fetch function for such routes, it should not apply the global prefix to their paths.
SDK Version: "@nestia/sdk": "^2.4.5",
Expected behavior: The sdk should not apply the global prefix to the paths included in the "exclude" option.
Actual behavior: The paths included in the "exclude" option should be ignored while setting the global prefix, but they are not being excluded in the generated sdk route.
@samchon i am sorry not to describe clearly , i am following your docs for manual setup (fresh nestjs + nestia manual setup) and docs about nestia swagger generator. #CMIIW but it doesn't mention about nestia.config.ts.
Summary
When calling the
app.setGlobalPrefix(...)
function innestia.config.ts
, it appears that the paths mentioned in the "exclude" option are also getting the global prefix (see example below). The correct behavior is that such paths should be excluded from the global prefix. When the SDK generates the fetch function for such routes, it should not apply the global prefix to their paths.SDK Version: "@nestia/sdk": "^2.4.5",
Expected behavior: The sdk should not apply the global prefix to the paths included in the "exclude" option.
Actual behavior: The paths included in the "exclude" option should be ignored while setting the global prefix, but they are not being excluded in the generated sdk route.
Code where the bug is occuring:
The text was updated successfully, but these errors were encountered: