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
Describe the bug
Boolean filters in the studio search display {{value}} instead of the actual TRUE or FALSE selected
To Reproduce:
Steps to reproduce the behavior:
Expected behavior
In this case (see screenshot below) I am expecting to see "Active is true" not "Active is {{value}}".
Screenshots
Which versions of Sanity are you using?
sanity versions @sanity/cli (global) 3.60.0 (up to date) @sanity/eslint-config-studio 4.0.0 (up to date) @sanity/vision 3.60.0 (up to date) sanity 3.60.0 (up to date)
What operating system are you using?
Windows 11.
Which versions of Node.js / npm are you running?
npm -v && node -v 10.9.0 v20.17.0
The text was updated successfully, but these errors were encountered:
Fixed in 3.62.0
Sorry, something went wrong.
No branches or pull requests
Describe the bug
Boolean filters in the studio search display {{value}} instead of the actual TRUE or FALSE selected
To Reproduce:
Steps to reproduce the behavior:
Expected behavior
In this case (see screenshot below) I am expecting to see "Active is true" not "Active is {{value}}".
Screenshots
Which versions of Sanity are you using?
What operating system are you using?
Windows 11.
Which versions of Node.js / npm are you running?
The text was updated successfully, but these errors were encountered: