The alps profile starts like below, but seems like it uses a differently configured jackson mapper, as the main one is configured to "enableEnumTranslation" ("Payment expected" instead of "PAYMENT_EXPECTED").
Another question: Is the ALPS JSON response actually valid ALPS? For example the alps-console project cannot read this file ( https://github.com/tkawa/alps-console ), and I did notice some differences, like missing "alps" root element, or "descriptors" instead of "descriptor"
Oliver Trosien opened DATAREST-683 and commented
Found while trying to document the enums of my REST API with ALPS.
See example including failing test here: https://github.com/otrosien/spring-alps-bug
The alps profile starts like below, but seems like it uses a differently configured jackson mapper, as the main one is configured to "enableEnumTranslation" ("Payment expected" instead of "PAYMENT_EXPECTED").
Affects: 2.4 GA (Gosling)
Referenced from: commits 35a86f7, cc7bc7a, 1f133fb, 75f1143
Backported to: 2.4.1 (Gosling SR1)
The text was updated successfully, but these errors were encountered: