Skip to content

Conversation

@renovate
Copy link

@renovate renovate bot commented Feb 13, 2021

This PR contains the following updates:

Package Change Age Confidence
routing-controllers ^0.8.1 -> ^0.11.0 age confidence

Release Notes

typestack/routing-controllers (routing-controllers)

v0.11.3

Compare Source

Changed
  • update dependencies to fix security vulnerabilities
  • update various dev-dependencies

v0.11.2

Compare Source

Changed
  • Reverted CurrentUserChecker generic

v0.11.1

Compare Source

Changed
  • Fixed Render decorator for Koa

v0.11.0

Compare Source

Changed
  • cookie package updated to 1.0.2 from 0.5.0
  • glob package updated to 11.0.0 from 10.2.2
  • reflect-metadata package updated to 0.2.2 from 0.1.13
  • Introduced UnprocessableEntityError
  • Dropped support for node versions below 20

v0.10.4

Compare Source

Changed
  • glob package updated to 10.1.0 from 10.2.2
Fixed
  • Fixed koa trailing slash handling
  • Fixed controller method inheritance

v0.10.3

Compare Source

Changed
  • glob package updated to 10.1.0 from 8.1.0
  • koa package updated to 2.14.2 from 2.14.1
  • koa-bodyparse package updated to 4.4.0 from 4.3.0
  • updated various dev dependencies
Fixed
  • Fixed koa uploaded file accessor

v0.10.2

Compare Source

Changed
  • glob package updated to 8.1.0 from 8.0.3
  • body-parser package updated to 1.20.2 from 1.20.1
  • multer package updated to 1.4.5-lts.1 from 1.4.4
  • updated various dev dependencies
Fixed
  • Added normalization to glob pattern resolver to fix Windows paths

v0.10.1

Compare Source

Changed
  • class-validator package updated to 0.14.0 from 0.13.2
    • Note: class-validator 0.14.0 enables forbidUnknownValues by default, but this is overridden in routing-controllers to prevent a breaking change. You can still enable it like before.
  • koa package updated to 2.14.1 from 2.13.4
  • updated various dev dependencies

v0.10.0

Compare Source

Added
  • isArray option for @QueryParam
Changed
  • class-transformer package updated to 0.5.1 from 0.3.1
  • class-validator package updated to 0.13.2 from 0.12.2
  • cookie package updated to 0.5.0 from 0.4.0
  • glob package updated to 8.0.3 from 7.1.4
  • express package updated to 4.18.2 from 4.17.1 and moved to optionalDependencies
  • express-session package updated to 1.17.1 from 1.17.3 and moved to optionalDependencies
  • body-parser package updated to 1.20.1 from 1.19.0
  • multer package updated to 1.4.4 from 1.4.2
  • koa package updated to 2.13.4 from 2.8.2
  • koa-multer package replaced with @koa/multer
  • koa-router package replaced with @koa/router
  • updated various dev dependencies
Fixed
  • Fixed parsing uuid as route parameter
  • Fixed target property not set during controller inheritance
  • Fixed NaN check for number route parameters
  • Added missing null value handling in parameters
  • Fixed middlewares not using the defined route prefix
0.9.0
Features
  • Add support for wildcard "all" routes (ref [#​536])
  • Controller inheritance - Added missing tests, code samples, and updated documentation (ref [#​578][#​301])
  • Added a useResponseClassTransformer global option (ref [#​329])
  • Through [#​329], it should now be possible to use classTransformer only for input (ref [#​179])
  • Added support for controller inheritance (ref [#​147])
  • Update all dependencies and changed it to use npm auto-update patches and minor versions (ex.: "class-validator": "^0.12.2", instead of "class-validator": "0.12.2" (ref [#​550])
  • Updated project tooling (ref [##​618])
Fixes
  • Input-validation bypass vulnerability (ref [#​518])
  • Fixed issue that would cause multiple route executions per request (ref [#​568])
  • Fixed export of SessionParam at index (ref [#​526])
  • Through [#​536], it should now prevent conflicts in routes names (ref [#​547])
  • Through [#​568], it should now prevent a single request triggering multiple route executions that would cause Error [ERR_HTTP_HEADERS_SENT]: Cannot set headers after they are sent to the client issue. (ref [#​491])
  • Fixed order of global interceptors (ref [#​543])
  • Fixed incorrect handling of rejected promises from Middleware.use() (ref [#​438])
  • Through [#​329], it should fix performance issue with big json result (ref [#​226])
  • Through [#​329], it should fix problem with mongoose model serialization (ref [#​149])
  • Local ValidationOptions are not overwriting global defaults (ref [#​618])
Documentation
  • Added TypeDI service decorator to example in README (ref [#​643])
  • Translate document to Chinese (ref [#​574])
  • Fix typo in README (ref [#​571])
  • Add another example for using the response directly (ref [#​546])
0.8.0 [BREAKING CHANGES]
Features
  • extract generic @Session() deocorator into @SessionParam() and @Session() (ref [#​335][#​348][#​407])
  • restore/introduce @QueryParams() and @Params() missing decorators options (ref [#​289][#​289])
  • normalize param object properties (for "queries", "headers", "params" and "cookies"), with this change you can easily validate query/path params using class-validator (ref [#​289][#​289])
  • improved params normalization, converting to primitive types is now more strict and can throw ParamNormalizationError (e.g. when number is expected but an invalid string (NaN) has been received) (ref [#​289][#​289])
0.7.7
Features
  • feat(ErrorHandling): add support for custom toJSON method in errors (ref #​325)
Fixes
  • fixed inconsistent roles parameter in authorizationChecker (ref #​308)
0.7.6
Fixes
  • fixed bugs with undefined result code behaviour
0.7.5
Fixes
  • fixed bugs with undefined result code behaviour
0.7.4
Fixes
  • fixed bugs with undefined result code behaviour
0.7.3
Features
  • Support for returning Buffer and streams from action handler (controller's method) (ref #​285)
  • Custom driver support (ref #​276)
Fixes
  • Directly calling response bug (ref #​286)
  • Missing parameter in @​BodyParam error message (ref #​284)
  • Sync and async auth checker bug (ref (ref #​283)
  • Handling different content-type responses in JsonController (ref #​277)
0.7.2
Fixes
  • Using @Authorization decorator with Koa caused 404 responses (ref #​240)
  • Allow throwing custom errors in authorizationChecker (ref #​233)
  • check auth permissions before accepting files for upload (ref #​251)
0.7.0 [BREAKING CHANGES]
  • some routing-controllers options has been changed and renamed
  • returned validation error value signature has changed
  • controllers and middlewares now can be specified in routing-controllers options
  • MiddlewareInterface was removed and instead ExpressMiddlewareInterface or KoaMiddlewareInterface should be used
  • ErrorMiddlewareInterface was renamed to ExpressErrorMiddlewareInterface
  • per-controller and per-action middlewares used in @UseBefore and @UseAfter now should not be marked with @Middleware decorator
  • @MiddlewareGlobalBefore() and @MiddlewareGlobalAfter() were removed and instead new signatures should be used: @Middleware({ type: "before" }) and @Middleware({ type: "after" })
  • named some decorator parameter names
  • added few new decorators to get all parameters like @QueryParams, @Params, @HeaderParams etc.
  • added @Authorized and @CurrentUser decorators
  • added new @Ctx decorator to use context with koa
  • @NullResultCode has been renamed to @OnNull, now supports error classes
  • @UndefinedResultCode has been renamed to @OnUndefined, now supports error classes
  • @EmptyResultCode has been removed. Use @OnUndefined decorator instead and return concrete types in your controllers.
  • added ability to create custom decorators
  • enabled validation by default
  • multiple bug fixes
  • codebase refactoring
  • removed JsonResponse and TextResponse decorators
0.6.10
Features
  • added integration with class-transform-validator for deserialization and auto validation request parameters
0.6.2
Features
  • made interceptors to support promises
0.6.1
Features
  • added interceptors support
0.6.0 [BREAKING CHANGES]
Features
  • middleware and error handlers support
  • everything packed into "routing-controllers" main export
  • added few more new decorators
Fixes
  • fixed multiple issues with param decorators
  • fixed multiple bugs
  • refactored core
Removals
  • removed parseJson from @Body decorator
  • removed ActionOptions
  • removed responseType from action options and added @JsonResponse and @TextResponse decorators
0.5.0
  • renamed package from controllers.ts to routing-controllers
  • added integration with constructor-utils for serialization and deserialization

v0.9.0

Compare Source

Features
  • Add support for wildcard "all" routes (ref [#​536])
  • Controller inheritance - Added missing tests, code samples, and updated documentation (ref [#​578][#​301])
  • Added a useResponseClassTransformer global option (ref [#​329])
  • Through [#​329], it should now be possible to use classTransformer only for input (ref [#​179])
  • Added support for controller inheritance (ref [#​147])
  • Update all dependencies and changed it to use npm auto-update patches and minor versions (ex.: "class-validator": "^0.12.2", instead of "class-validator": "0.12.2" (ref [#​550])
  • Updated project tooling (ref [##​618])
Fixes
  • Input-validation bypass vulnerability (ref [#​518])
  • Fixed issue that would cause multiple route executions per request (ref [#​568])
  • Fixed export of SessionParam at index (ref [#​526])
  • Through [#​536], it should now prevent conflicts in routes names (ref [#​547])
  • Through [#​568], it should now prevent a single request triggering multiple route executions that would cause Error [ERR_HTTP_HEADERS_SENT]: Cannot set headers after they are sent to the client issue. (ref [#​491])
  • Fixed order of global interceptors (ref [#​543])
  • Fixed incorrect handling of rejected promises from Middleware.use() (ref [#​438])
  • Through [#​329], it should fix performance issue with big json result (ref [#​226])
  • Through [#​329], it should fix problem with mongoose model serialization (ref [#​149])
  • Local ValidationOptions are not overwriting global defaults (ref [#​618])
Documentation
  • Added TypeDI service decorator to example in README (ref [#​643])
  • Translate document to Chinese (ref [#​574])
  • Fix typo in README (ref [#​571])
  • Add another example for using the response directly (ref [#​546])

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/routing-controllers-0.x branch from 297b741 to 8ef6498 Compare November 3, 2021 18:48
@renovate renovate bot force-pushed the renovate/routing-controllers-0.x branch from 8ef6498 to 391a024 Compare June 18, 2022 19:29
@renovate
Copy link
Author

renovate bot commented Jun 18, 2022

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: typescript-express-template@1.0.0
npm ERR! Found: class-transformer@0.3.2
npm ERR! node_modules/class-transformer
npm ERR!   class-transformer@"^0.3.2" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer class-transformer@"^0.5.1" from routing-controllers@0.10.2
npm ERR! node_modules/routing-controllers
npm ERR!   routing-controllers@"^0.10.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/renovate-cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate-cache/others/npm/_logs/2023-03-16T23_48_59_772Z-debug-0.log

@renovate renovate bot force-pushed the renovate/routing-controllers-0.x branch from 391a024 to 3ddf8a7 Compare March 16, 2023 23:49
@renovate renovate bot changed the title Update dependency routing-controllers to ^0.9.0 Update dependency routing-controllers to ^0.10.0 Mar 16, 2023
@renovate renovate bot force-pushed the renovate/routing-controllers-0.x branch from 3ddf8a7 to 2e23f49 Compare February 14, 2025 22:53
@renovate renovate bot changed the title Update dependency routing-controllers to ^0.10.0 Update dependency routing-controllers to ^0.11.0 Feb 14, 2025
@renovate
Copy link
Author

renovate bot commented Feb 14, 2025

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: typescript-express-template@1.0.0
npm ERR! Found: class-transformer@0.3.2
npm ERR! node_modules/class-transformer
npm ERR!   class-transformer@"^0.3.2" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer class-transformer@"^0.5.1" from routing-controllers@0.11.3
npm ERR! node_modules/routing-controllers
npm ERR!   routing-controllers@"^0.11.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /runner/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /runner/cache/others/npm/_logs/2025-11-18T23_55_24_503Z-debug-0.log

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant