Allow configuration of RelProvider in RepositoryResourceMappings [DATAREST-1076]

[spring-projects-issues]

Erick opened DATAREST-1076 and commented

Currently the RepositoryResourceMappings class creates a new instance of the EvoInflectorRelProvider, and the other constructor has been marked package protected leaving no way to customize the RelProvider.

public RepositoryResourceMappings(Repositories repositories, PersistentEntities entities, RepositoryDetectionStrategy strategy) {
    this(repositories, entities, new EvoInflectorRelProvider(), strategy);
}

---

Backported to: 2.6.4 (Ingalls SR4)

[spring-projects-issues]

Oliver Drotbohm commented

Good point, we can certainly do that. RepositoryRestMvcConfiguration already accesses the RelProvider set up by Spring HATEOAS and could forward that to the RepositoryResourceMappings. Do you think that'd be enough for your customization needs?

[spring-projects-issues]

Oliver Drotbohm commented

Looks like forwarding the configured RelProvider instances is not an option as the RepositoryResourceMapping instances act as a source for the RepositoryRelProvider which would then create a resolution cycle. I'll go ahead with the constructor exposure though. I'll also add a hook to RepositoryRestConfiguration so that the RelProvider to be used as default for repositories can be configured without having to extend RepositoryRestMvcConfiguration using a simple RepositoryRestConfigurer