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
Enforce standard Java types in YamlProcessor #26530
Labels
in: core
Issues in core modules (aop, beans, core, context, expression)
type: enhancement
A general enhancement
Milestone
Comments
bclozel
added
in: core
Issues in core modules (aop, beans, core, context, expression)
type: enhancement
A general enhancement
labels
Feb 9, 2021
This was referenced Mar 7, 2021
Merged
This was referenced Mar 14, 2021
This was referenced Mar 16, 2021
Open
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
in: core
Issues in core modules (aop, beans, core, context, expression)
type: enhancement
A general enhancement
spring-beans
ships aYamlProcessor
that's used as a base class byYamlMapFactoryBean
andYamlPropertiesFactoryBean
. These implementations have a clear use case: mapping application-internal Yaml documents for configuration or infrastructure purposes.Since this use case rarely requires extended types support from the underlying library, and since we're offering ways to list custom types (since #25152), we'll restrict to java standard types only by default. This simplifies the setup and focuses the abstract class on the core use cases.
Developers can leverage #25152 to allow custom types like this:
The text was updated successfully, but these errors were encountered: