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

release: version 11.0.0 #14177

Draft
wants to merge 187 commits into
base: master
Choose a base branch
from
Draft

release: version 11.0.0 #14177

wants to merge 187 commits into from

Conversation

kamilmysliwiec
Copy link
Member

@kamilmysliwiec kamilmysliwiec commented Nov 20, 2024

PR Checklist

Please check if your PR fulfills the following requirements:

PR Type

What kind of change does this PR introduce?

  • Bugfix
  • Feature
  • Code style update (formatting, local variables)
  • Refactoring (no functional changes, no api changes)
  • Build related changes
  • CI related changes
  • Other... Please describe: v11 release

What is the current behavior?

Issue Number: N/A

What is the new behavior?

Dependency upgrades

Features or improvements

Bug fixes

Nit

Other important changes/upgrades in the ecosystem

Does this PR introduce a breaking change?

  • Yes
  • No

Other information

notusertelken and others added 30 commits January 19, 2022 22:30
When only a single metadata value is present in the list of targets for
`Reflector#getAllAndMerge`, that value gets wrapped in an array if it is
not already an array or an object.
Previously, single values were returned as is, so the method could
actually return any value. Now the method always returns an array or an
object as indicated by its return type.
This also fixes the return type of both `getAll` and `getAllAndMerge`
when using the strongly typed `ReflectableDecorator<T>`.

Fixes #12231
Microservices are now able to be created by getting their options
from within the DI container itself. This has been a long requested
feature of developers and I finally had some time to work through how
we could possibly let this happen.
fixed issue that with type option which is not already converted,
any other option cannot be applied to plainToClass

Closes #12763
Transforming numeric values in validationpipe is incorrect when value is undefined

closes #12864
Co-authored-by: Vinicius Lourenço <12551007+H4ad@users.noreply.github.com>
Multer errors may include a 'field' property for certain errors. Pass it
along into the error message.
Add the possible `field` property to the `error` arg in
`transformExecption`.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.