Skip to content

Support generalized query language on back end #2217

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.

Sign up for GitHub

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

Jump to bottom
Closed
ketang opened this issue Jun 9, 2022 · 3 comments
Closed

Support generalized query language on back end #2217

ketang opened this issue Jun 9, 2022 · 3 comments
Assignees
@Emyrk
Labels
api Area: HTTP API site Area: frontend dashboard
Milestone
Community MVP

Comments

@ketang
Copy link
Contributor

ketang commented Jun 9, 2022

Per #2176 some filters applied to the search are transformed from terms in the search query to different parameters on the back end. What we should do instead is support a fully general query/search string language that can be passed to the back end via the API or CLI so that those clients have the same power as web UI users.

@Emyrk
@ketang ketang mentioned this issue Jun 9, 2022
Closed
@Emyrk Emyrk self-assigned this Jun 10, 2022
@misskniss misskniss added api Area: HTTP API site Area: frontend dashboard labels Jun 14, 2022
@Emyrk
Copy link
Member

Emyrk commented Jun 14, 2022

Completed here: #2232

@Emyrk Emyrk closed this as completed Jun 14, 2022
@Emyrk
Copy link
Member

Emyrk commented Jun 14, 2022

CLI work still needed to support raw query

@misskniss misskniss added this to the Community MVP milestone Jun 16, 2022
@ketang
Copy link
Contributor Author

ketang commented Jul 1, 2022

#2644 is the next step

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Emyrk Emyrk

Labels
api Area: HTTP API site Area: frontend dashboard
Projects
None yet
Milestone
Community MVP
Development

No branches or pull requests
3 participants
@ketang @misskniss @Emyrk