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
Given that DotSearchFilter converts POST /Users/.search into GET /Users with query params, the obvious approach is to only handle the GET endpoint. Problem is that I found no way of getting access to a SearchRequest model built from the query params. If I handle just the POST /Users/.search, it works out nicely mapping the json body to a SearchRequest model, however this does not work out well when filters are specified as query params
The text was updated successfully, but these errors were encountered:
@andreim11, it's true that the SearchRequest model is not easily accessible once DotSearchFilter.filter() is invoked. Could you give some details about your use case and the problem you're trying to solve? Are you trying to interface with a particular product?
Given that DotSearchFilter converts POST /Users/.search into GET /Users with query params, the obvious approach is to only handle the GET endpoint. Problem is that I found no way of getting access to a SearchRequest model built from the query params. If I handle just the POST /Users/.search, it works out nicely mapping the json body to a SearchRequest model, however this does not work out well when filters are specified as query params
The text was updated successfully, but these errors were encountered: