When scanning for components one needs to provide TypeFilter-s for including/excluding candidates. There are currently 2 useful implementations that are defined as private classes with public constructors - namely org.springframework.data.repository.config.RepositoryComponentProvider.InterfaceTypeFilter and org.springframework.data.repository.config.RepositoryComponentProvider.AllTypeFilter. After examining their code there does not seem to be any special reason for "hiding" them - especially since they are so useful. I propose making them public and perhaps moving them to their own class file instead of being inner classes. This should pose no backward compatibility issues since existing code does not "see" these classes anyway.
DATACMNS-1372 Expose InterfaceTypeFilter and AllTypeFilter classes as public ("duplicates")
The text was updated successfully, but these errors were encountered:
I've moved your previous report to the Spring Data project since these are not core framework classes. Any specific follow-up at the core framework level can be dealt with here but let's leave the initial round of review over there in Spring Data.