Repository navigation
feat(search): filter by date, tag, origin and language - #695
Merged
Merged
Conversation
GET /search takes from/to, tag, origin and language (the Library's filters, via library.where) and keeps every kind of hit to the assets that have them; the MCP search tool takes date_from/date_to (day, month or year), tags, origins and languages. The search page gets compact Assets controls at the top of the filter panel, empty until picked, typed filters in the box, chips, the URL and saved searches carry them. A recording-set restriction (such as the object filter) now applies to screen, file, object and description hits too, not only to what was said. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QFUNzy1QZy5HhKAyJxTAYJ
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Requested by Adeel · project thread
Description
Before: search could not be narrowed by when an asset is from, its tags, where it came from or its language; those filters existed only in the Library.
After:
GET /searchtakesfrom/to,tag,originandlanguage(the Library's filters, throughlibrary.where) and keeps every kind of hit to the assets that match. The MCPsearchtool takesdate_from/date_to(a day, month or year),tags,originsandlanguages. The search page has compact Assets controls at the top of the filter panel, empty until picked; filters can also be typed in the box, and they show as chips and carry through the URL and saved searches.A recording-set restriction (such as the object filter) now applies to screen, file, object and description hits too, not only to what was said.
Motivation and Context
Personal feature plan: find things by date, tag, source and language.
Types of changes
!in the title)Checklist:
make hookschecks it on commit).docs/accordingly.changelog.d/search-filters.md, per build(release): changelog fragments in changelog.d/ instead of one Unreleased section #581.Done questions (AGENTS.md)
searcharguments..envedit or manual step.make openapi).library.wherefilters reused.Local CI:
pytest tests/api/test_search.py tests/api/test_mcp.py tests/api/test_unnamed_faces.py(29 passed), ruff, mypy, jest__tests__/search*(23 passed),tsc --noEmit,ci/check_requirements.pyall clean; OpenAPI regenerated with no drift.Generated by Claude Code