Repository navigation
fix(query): read a chat id with @ as one term, unquoted - #269
Merged
Merged
Conversation
`chat:<n>@lid` failed with query.unsupported-operator: the tokenizer kept `@` inside a word only before a dotted host, so `@lid` became Lucene's minimum-should-match. An `@` followed by a letter now stays in the term. `alpha@2` and `(a b)@2` are still refused. Every WhatsApp user who pastes a chat id into `chat:` hit this (UX-86 in the max-cli journal). Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Merged
leemour
added a commit
that referenced
this pull request
Oct 20, 2026
Dates the Unreleased section (chat ids with @ parse unquoted, #269) as 0.47.3. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
leemour
added a commit
to WireCatLabs/cli-core
that referenced
this pull request
Oct 20, 2026
) Picks up the cli-base fix (WireCatLabs/cli-base#269, released in 0.47.3): `chat:133…@lid` and `chat:120…@g.us` parse as one term instead of failing with `query.unsupported-operator`. - cli-base dev pin 0.47.0 → 0.47.3; peer range now `>=0.47.3 <0.48.0`, so wa and tg must raise their own cli-base pin with this release. - Test in `registry.test.ts`: a chat id parses through the message fields; `(alpha beta)@2` is still refused. - `email` field help, `docs/mentions.md`, regenerated `docs/search/query-language.md`: emails unquoted (the "@ is an operator" note was already false for addresses). - `docs/dev/STANDARD.md` regenerated from cli-base 0.47.3 standards. Checks: lint, typecheck, test (5845 passed), docs:check. Source: UX-86, report `max-cli/docs_ai/research/2026-10-20-whatsmeow-coverage-and-tg-alignment.md`. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This was referenced Oct 20, 2026
leemour
added a commit
to WireCatLabs/whatsapp-cli
that referenced
this pull request
Oct 20, 2026
Bumps `@wirecat/cli-core` to 0.375.0 and `@wirecat/cli-base` to 0.47.3 so `chat:<n>@lid` and `chat:<n>@g.us` work without quotes (previously `query.unsupported-operator`). - WireCatLabs/cli-base#269 - WireCatLabs/cli-core#1691 Also removes the quoting workaround from docs and `bin/live-expired-file`, and adds a CHANGELOG line. Lint, typecheck, tests (512 passed), docs, standards and parity checks pass locally. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
leemour
added a commit
to WireCatLabs/tg-cli
that referenced
this pull request
Oct 20, 2026
Bumps the exact pins `@wirecat/cli-core` 0.372.0 → 0.375.0 and `@wirecat/cli-base` 0.47.0 → 0.47.3 (cli-core 0.375.0 requires cli-base >=0.47.3). Brings the query fix: an `@` followed by a letter stays in a term, so e-mails without a dot after the `@` and chat ids work unquoted. Docs and the tg-cli skill now show `email:ana@example.com`. CHANGELOG has a Fixed line. Tests: lint, typecheck, test (1573 passed), docs:check and parity:check pass locally. Links: WireCatLabs/cli-base#269, WireCatLabs/cli-core#1691 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
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
1 participant
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.
chat:133…@lidwas refused withquery.unsupported-operator: the tokenizer kept@inside a word only before a dotted host (an email), so@lidwas read as minimum-should-match. Now an@followed by a letter stays in the term.chat:…@lid,chat:…@g.us,chat:…@s.whatsapp.netparse as one term.alpha@2,(alpha OR beta)@2,chat:133@2.@is untouched.Source: UX-86 in the wa status journal, report
max-cli/docs_ai/research/2026-10-20-whatsmeow-coverage-and-tg-alignment.md. cli-core picks this up with its next cli-base bump.Checks:
pnpm lint,pnpm typecheck,pnpm test(773 passed).🤖 Generated with Claude Code