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
For example, I'm working on top of a legacy database which has all it's column names in german. I use alias_attritbute to map english names to the german column names. If I were to use Ransack I would have to support using the german attributes as query params.
The request /api/locations?q[code_eq]=bremen will not work. As it will construct the query as where orte.code = 'bremen', while it should be translated to where orte.bezeichnung = 'bremen' .
The text was updated successfully, but these errors were encountered:
Hello @martndemus, thank you for highlighting this. It seems like an edge case feature request rather than a bug with the current code. I do not plan to work on it, but encourage you to make a pull request it if it is worthwhile for you to add it to Ransack. Cheers!
For example, I'm working on top of a legacy database which has all it's column names in german. I use
alias_attritbute
to map english names to the german column names. If I were to use Ransack I would have to support using the german attributes as query params.With this example:
The request
/api/locations?q[code_eq]=bremen
will not work. As it will construct the query aswhere orte.code = 'bremen'
, while it should be translated towhere orte.bezeichnung = 'bremen'
.The text was updated successfully, but these errors were encountered: