We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When I set examples to output ">=" in filter part, I confirmed Gemini returns following URL parameter as expected.
fields=users.name,user_order_facts.lifetime_orders&f[user_order_facts.lifetime_orders]=>=10
However, when explore comes up, the embedded url includes following URL parameters:
&fields=users.name,user_order_facts.lifetime_orders&f[user_order_facts.lifetime_orders]=>
So "=10" has gone from the url parameter and actual filter in Explore displays Livetime Order is any value.
Livetime Order is any value
After some investigation, I suspects it's gone during the exploreUrl creation:
exploreUrl.split('&').map((param) => { const [key, ...rest] = param.split('=') // paramsObj[key] = rest.join('=') if (key === 'filter_expression' || key === 'dynamic_fields') { // console.log('rest', rest) paramsObj[key] = rest.join('=') } else { paramsObj[key] = param.split('=')[1] }
It split by "=" and therefore ">=" (and "<=") won't be handled as expected.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
When I set examples to output ">=" in filter part, I confirmed Gemini returns following URL parameter as expected.
fields=users.name,user_order_facts.lifetime_orders&f[user_order_facts.lifetime_orders]=>=10
However, when explore comes up, the embedded url includes following URL parameters:
&fields=users.name,user_order_facts.lifetime_orders&f[user_order_facts.lifetime_orders]=>
So "=10" has gone from the url parameter and actual filter in Explore displays
Livetime Order is any value
.After some investigation, I suspects it's gone during the exploreUrl creation:
It split by "=" and therefore ">=" (and "<=") won't be handled as expected.
The text was updated successfully, but these errors were encountered: