You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, this is more a question for a better way than what we did with a small 'hack'.
Spring-Data-Rest does a lot of things out-of-the-box. And binding parameters to do a queryDsl-search is also cool and we would like to use it.
Unfortunately our company has some 'Rest-Guidelines' mentioning that parameters have to be 'snake_case' instead of 'camelCase'. The problem is, that the search has no mapping for that and will not work.
So I 'fixed' it in an ugly way and want to know how can we solve this issue in a better way.
QuerydslAwareRootResourceInformationHandlerMethodArgumentResolver is extendable
the configuration that creates the RootResourceInformationHandlerMethodArgumentResolver as a bean could check for an existing bean already provided, maybe with '@ConditionalOnMissingBean'
Affects: 2.6 GA (Ingalls)
1 votes, 2 watchers
The text was updated successfully, but these errors were encountered:
Joerg Bellmann opened DATAREST-1011 and commented
Hi, this is more a question for a better way than what we did with a small 'hack'.
Spring-Data-Rest does a lot of things out-of-the-box. And binding parameters to do a queryDsl-search is also cool and we would like to use it.
Unfortunately our company has some 'Rest-Guidelines' mentioning that parameters have to be 'snake_case' instead of 'camelCase'. The problem is, that the search has no mapping for that and will not work.
So I 'fixed' it in an ugly way and want to know how can we solve this issue in a better way.
The small showcase project is on github..
The ugly part starts here.
It would already be helpful if :
@ConditionalOnMissingBean
'Affects: 2.6 GA (Ingalls)
1 votes, 2 watchers
The text was updated successfully, but these errors were encountered: