A new annotation for a model/entity/data class which cuts down on boilerplate.
Currently if you are creating a quick simple @RepositoryRestResource interface and you for go defining any specific signatures, you end up with a lot of empty interfaces with repeated code.
To cut down on the boilerplate for such instances it would be nice to just add the @RepositoryRestResource(or a new annotation) to the actual model/entity/data class. This annotation would effectively be generating the same code the current @RepositoryRestResource is generating today, but without the need for nearly empty interfaces.
It may require an additional parameter for the type of repository that you are looking to create as well. ex. PagingAndSortingRepository vs. any other repository.
I don't think we want to go down that route. I strongly disagree that you're dealing with empty interfaces. Repository are a key element of your domain model and in any real world application contain way more than just CRUD operations. It's query methods, custom implementations etc. I.e. what you ask for is over-optimization for a hello world scenario that only applicable to the simplest demo cases