Provide configuration property metadata for binding to Map<String, RichType> and List<RichType>
See original GitHub issueOne example of such a Map
is in Spring Cloud stream. As things stand, there’s no metadata for any of the properties on BindingProperties
. I think it would be interesting to explore the possibility of providing metadata for those properties, perhaps using a wildcard for the key in the map:
spring.cloud.stream.bindings.*.content-type
spring.cloud.stream.bindings.*.destination
spring.cloud.stream.bindings.*.group
…
For this to be useful, we’d need a corresponding enhancement in each of the IDE plugins.
Issue Analytics
- State:
- Created 6 years ago
- Reactions:8
- Comments:13 (13 by maintainers)
Top Results From Across the Web
Configuration Metadata - Spring
Spring Boot jars include metadata files that provide details of all supported configuration properties. The files are designed to let IDE ...
Read more >A Guide to Spring Boot Configuration Metadata - Baeldung
Learn about the Spring Boot Configuration Processor and the associated JSON metadata files that document each property's meaning, ...
Read more >Mapping configuration to objects - Quarkus
A config mapping requires an interface with minimal metadata configuration and annotated with the @io.smallrye.config.ConfigMapping annotation.
Read more >spring-boot-configuration-processor: How to generate or ...
How to generate or provide metadata for externally provided configuration properties used with variable prefixes using the spring-boot- ...
Read more >Binding external configurations to POJO classes - CalliCoder
External configurations allow you to work with the same code in different ... Spring Boot application loads configuration properties from ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I can’t speak for Eclipse but IJ has support for this for ages on
.properties
. There isn’t for yaml at the moment though. To be clear, we’re now considering this with higher priority given the potential binding change.The lack of this metadata allowed the mistake that @dreis2211 has fixed in this pull request to slip through. Our Asciidoctor extension only validates maps on a best-effort basis. The prefix,
spring.security.saml2.relyingparty.registration
, matched and there’s no metadata to tell it what properties each entry in the map may have so it was unable to detect and report the error.