Skip to content

Provide an alternative way to group auto-configuration together in the report #9077

@snicoll

Description

@snicoll

Now that we have a reactive flavour for our data stores, we can see things like ReactiveFooDataAutoConfiguration alongside FooDataConfiguration. The naming sounds about right but information about foo are now split in two distinct areas of the auto-configuration report as we order them alphabetically.

One idea would be to group them by package which works for some part but not for everything as Data auto-configuration typically is split in two (a package for the data store when Spring Data isn't available and the Spring Data specific bits are located in another package).

Maybe we need a better semantic to group auto-configurations together?

Metadata

Metadata

Assignees

No one assigned

    Labels

    status: declinedA suggestion or change that we don't feel we should currently apply

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions