Hi team! I’m trying to use `sort_by` + `eval_` fea...
# community-help
d
Hi team! I’m trying to use
sort_by
+
eval_
feature, but for some reason it throw “Only upto 3 sort fields are allowed” error 🤔 My sort_by string looks like
Copy code
_eval(field:=[`foo`,`bar`,`foo bar`]):desc,_text_match:desc,other_field:desc'`
Could it be because of the space?
k
I suspect a parsing bug. Could you try maybe removing the space and/or backticks?
Basically try simplifying the expression to see if that helps. If it does, then there is an edge case we are not handling.
👀 1
Also, there is an additional backtick at the end after
other_field:desc'
d
You’re right, it’s my problem with copy and paste 🐸
Copy code
_eval(field:=[`foo`]):desc,_text_match:desc,other_field:desc
_eval(field:=[`foo:bar`]):desc,_text_match:desc,other_field:desc
_eval(field:=[`foo bar`]):desc,_text_match:desc,other_field:desc
Work fine, but
Copy code
_eval(field:=[`foo`, `bar`]):desc,_text_match:desc,other_field:desc
_eval(field:=[foo, bar]):desc,_text_match:desc,other_field:desc
don’t
k
So what's the issue? Space?
d
Comma
It looks like parser splits
sort_by
by comma
k
Sorry can you explain visually where the problem is 😄
Copy code
`foo`, `bar`
This part?
d
Let me return with reproducible example 🌚
👍 1
if
eval_
contains comma it’s acting weirdly
k
Got it, thanks. Can you also please create an issue on Github? We are just cleaning up some last mile issues for 0.25 release. We will start cracking on recent bugs soon after the release.
🙌 1
🤞 1
d