It would be handy, for example
@AutoConfiguration
@EnableConfigurationProperties({MyPropA.class, MyPropB.class})
can be written as
@AutoConfiguration(properties = {MyPropA.class, MyPropB.class})
Comment From: wilkinsona
Thanks for the suggestion. While auto-configuration and configuration properties are often used together, that isn't always the case and we have many auto-configuration classes in Spring Boot that don't rely on configuration property binding. As such, I don't think we should add @EnableConfigurationProperties to @AutoConfiguration. Let's see what the rest of the team thinks.
Comment From: mhalbritter
I agree with you, Andy. I think there's a risk that @AutoConfiguration becomes a god-annotation.
Comment From: philwebb
+1. I also think these kind of shortcuts aren't as critical in auto-configuration classes since the majority of Spring Boot users rely on, but don't typically directly use @AutoConfiguration.
Comment From: philwebb
Looks like we have enough of a consensus to decline this one. Thanks anyway for the suggestion @ttddyy!