Sort mapping does not consider Jackson customizations in field names [DATAREST-883]

[spring-projects-issues]

Oliver Drotbohm opened DATAREST-883 and commented

Currently the Sort instance derived from an HTTP request gets the fields forwarded to the repository without any Jackson customizations (e.g. field name customizations) applied.

That means that although you might have customized the field name in the representation, the request parameter for the sort would still expose the underlying property names

---

Affects: 2.4.4 (Gosling SR4), 2.5.2 (Hopper SR2), 2.6 M1 (Ingalls)

Issue Links:

• DATAREST-909 Revert Jackson-aware Sort and Pageable translation in Hopper and Gosling release trains

Referenced from: pull request #222

Backported to: 2.5.3 (Hopper SR3), 2.4.5 (Gosling SR5)

[spring-projects-issues]

Andrii Neverov commented

It looks like the fix has been reverted and the issue is still present with Spring Boot 1.5.8.RELEASE. Can this request be reopened?

[spring-projects-issues]

Oliver Drotbohm commented

No, as it has been marked fixed against released versions and shows up in those version's changelog. The original fix has been reversed in favor of a better fix (see the commits linked to from the right bar). If you still see erroneous behaviour in current Ingalls, please open a new ticket describing the exact problem you're seeing