feat(messages): add q filtering across API and clients - #735
Draft
jiashuoz wants to merge 12 commits into
Draft
Conversation
Co-Authored-By: Kimi <noreply@moonshot.ai>
Co-Authored-By: Kimi <noreply@moonshot.ai>
Co-Authored-By: Kimi <noreply@moonshot.ai>
Co-Authored-By: Kimi <noreply@moonshot.ai>
Co-Authored-By: Kimi <noreply@moonshot.ai>
Co-Authored-By: Kimi <noreply@moonshot.ai>
Co-Authored-By: Kimi <noreply@moonshot.ai>
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.
Summary
qtolist_messageswith the v1 fieldslabel,from,subject, andcreatedqin pagination cursorsSemantics
Date-only values represent the entire UTC calendar day: equality uses
[start, end), inequality uses the inverse, and ordering compares against the documented day boundary.has:attachmentis deliberately deferred. The current attachment JSON is not an authoritative normalized count for all inbound MIME, so exposing it now would create incorrect filtering semantics. It remains rejected as an unknown field until the required expand/backfill/contract migration is designed.Validation
go build ./...go test ./internal/filterquery/... ./internal/identity/... ./internal/httpapi/... -count=1 -parallel=1make spec-check generate-sdk-check openapi-compat-checkStack
PR 2 of 2, stacked on
feat/filter-query-language-core. After PR 1 merges, retarget this PR tomain.