Skip to content
New issue

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

query-string search should work with vocabulary token instead of value #108

Open
jackahl opened this issue May 5, 2022 · 0 comments
Open
Assignees

Comments

@jackahl
Copy link
Member

jackahl commented May 5, 2022

As the vocabulary in a token is the proper unique identifier for that term it should be the thing that is stored in in the volto frontend. Currently querystring uses the value of that term to assemble the search, which potentially could lead to issues as these can theoretically be of datatypes that are not reasonable to store in the frontend (e.g. python objects). Therefor especially when used with restapi and volto querystring searches should mostly rely on the vocabulary token.

The prerequisites to implement this are already available in #107.

@jackahl jackahl self-assigned this May 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant