Repository navigation
fix(search): take a WhatsApp chat id unquoted, on cli-base 0.47.3 - #1691
Merged
Merged
Conversation
cli-base 0.47.3 keeps an `@` followed by a letter inside a term, so `chat:<n>@lid` and `chat:<n>@g.us` no longer fail with query.unsupported-operator. cli-core now requires cli-base >=0.47.3 so a CLI cannot pair it with a parser that still refuses them. The `email` field help and docs/mentions.md said emails must be quoted because `@` is an operator; that was already false for addresses, and the examples are unquoted now. STANDARD.md is regenerated from the cli-base 0.47.3 standards (`--qr-file` gone, `--alias` added). 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
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.
Picks up the cli-base fix (WireCatLabs/cli-base#269, released in 0.47.3):
chat:133…@lidandchat:120…@g.usparse as one term instead of failing withquery.unsupported-operator.>=0.47.3 <0.48.0, so wa and tg must raise their own cli-base pin with this release.registry.test.ts: a chat id parses through the message fields;(alpha beta)@2is still refused.emailfield help,docs/mentions.md, regenerateddocs/search/query-language.md: emails unquoted (the "@ is an operator" note was already false for addresses).docs/dev/STANDARD.mdregenerated 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