From a418487f3c0b9bf33283e453f19e9554173307cf Mon Sep 17 00:00:00 2001 From: Trenton Holmes <797416+stumpylog@users.noreply.github.com> Date: Tue, 18 Aug 2026 09:28:36 -0700 Subject: [PATCH] test(search): replace stale docs reference in id-field fold docstring The TestUnregisteredIdFieldFoldsToLiteralText docstring pointed readers at docs/usage.md's advanced-search note about the dropped *_id prefixes, which a later commit removed. State the rationale directly instead: the *_id fields were always internal index columns (v2 consumed them for permission filtering and its own criteria), and their queryability as search syntax was an accident of whoosh resolving any schema field name. Co-Authored-By: Claude Fable 5 Claude-Session: https://claude.ai/code/session_01WMsn6DgzbvSqh1pwy66VVF --- src/documents/tests/search/test_acceptance.py | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) diff --git a/src/documents/tests/search/test_acceptance.py b/src/documents/tests/search/test_acceptance.py index 923a021ab..67493939d 100644 --- a/src/documents/tests/search/test_acceptance.py +++ b/src/documents/tests/search/test_acceptance.py @@ -337,10 +337,13 @@ class TestRfc3339TZDateRange: class TestUnregisteredIdFieldFoldsToLiteralText: """tag_id, owner_id, etc. are intentionally excluded from the - FieldRegistry - whoosh-compat parity leniency folds them into a literal - text search rather than raising a diagnostic/400 (see docs/usage.md's - advanced-search section). Prove the fold is inert against real data, not - just that parsing doesn't raise.""" + FieldRegistry: they were always internal index columns (v2 consumed + them for permission filtering and its own criteria), and their + queryability as search syntax was an accident of whoosh resolving any + schema field name. whoosh-compat parity leniency folds them into a + literal text search rather than raising a diagnostic/400. Prove the + fold is inert against real data, not just that parsing doesn't + raise.""" def test_tag_id_query_matches_nothing( self,