Field names are not correctly handled in view filters #2233

New Issue

waza-ari · 2024-03-23T13:13:21Z

waza-ari commented

2024-03-23 13:13:21 +00:00

Description

When trying to create a View including a filter, some field names are not translated correctly. The following filter for example is stored as is, which will yield an internal server error as the column doesn't exist:

done = false || (done = true && doneAt > 'now-14d')

Manually editing the filter to

done = false || (done = true && done_at > 'now-14d')

yields the expected result

Vikunja Version

Unstable

Browser and version

No response

Can you reproduce the bug on the Vikunja demo site?

Yes

Screenshots

No response

### Description When trying to create a View including a filter, some field names are not translated correctly. The following filter for example is stored as is, which will yield an internal server error as the column doesn't exist: ``` done = false || (done = true && doneAt > 'now-14d') ``` Manually editing the filter to ``` done = false || (done = true && done_at > 'now-14d') ``` yields the expected result ### Vikunja Version Unstable ### Browser and version _No response_ ### Can you reproduce the bug on the Vikunja demo site? Yes ### Screenshots _No response_

waza-ari added the

kind/bug

label 2024-03-23 13:13:21 +00:00

konrad commented

2024-03-28 20:57:31 +00:00

Which fields are not translated?