mirror of
https://github.com/ArchiveBox/ArchiveBox.git
synced 2026-04-25 09:06:02 +03:00
[PR #1457] [MERGED] Implement searching individual fields #4443
Labels
No labels
expected: maybe someday
expected: next release
expected: release after next
expected: unlikely unless contributed
good first ticket
help wanted
pull-request
scope: all users
scope: windows users
size: easy
size: hard
size: medium
size: medium
status: backlog
status: blocked
status: done
status: idea-phase
status: needs followup
status: wip
status: wontfix
touches: API/CLI/Spec
touches: configuration
touches: data/schema/architecture
touches: dependencies/packaging
touches: docs
touches: js
touches: views/replayers/html/css
why: correctness
why: functionality
why: performance
why: security
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/ArchiveBox#4443
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
📋 Pull Request Information
Original PR: https://github.com/ArchiveBox/ArchiveBox/pull/1457
Author: @sclu1034
Created: 6/19/2024
Status: ✅ Merged
Merged: 8/20/2024
Merged by: @pirate
Base:
dev← Head:feat/search-fields📝 Commits (2)
10f0c4aImplement searching individual fields75018edMerge branch 'dev' into feat/search-fields📊 Changes
2 files changed (+35 additions, -2 deletions)
View changed files
📝
archivebox/core/views.py(+26 -2)📝
archivebox/templates/core/public_index.html(+9 -0)📄 Description
Summary
This adds a rudimentary implementation of #1453.
So far, this only changes the search box on the public view, as the custom form and corresponding logic there were relatively simple to track down and change.
As far as I can tell, the one on the admin page uses Django's built-in functionality instead, and I didn't see any immediate way to change that logic.
The current list of supported fields is mostly just based on the placeholder in the search input, but adding more metadata fields should be trivial.
Another interesting change could be to have the
Metadataoption run ripgrep, but restricted toindex.jsonvia glob (or the equivalent for other backends), but that would require a change in the search backends'search()function signature.Related issues
#1453
Changes these areas
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.