Skip to content

add telegram notification configuration guide documents.#10

Merged
brokermr810 merged 1 commit into
OpenByteInc:mainfrom
p369349074:telegram-notification-docts
Jan 12, 2026
Merged

add telegram notification configuration guide documents.#10
brokermr810 merged 1 commit into
OpenByteInc:mainfrom
p369349074:telegram-notification-docts

Conversation

@p369349074

Copy link
Copy Markdown
Contributor

add the documents for signal to telegram notification configuration guide documents.

@brokermr810
brokermr810 merged commit bb45248 into OpenByteInc:main Jan 12, 2026
2 checks passed
woohaha pushed a commit to woohaha/QuantDinger that referenced this pull request May 16, 2026
Fixes review issue OpenByteInc#10 — /list previously showed `—` for every code
because cmd_watch always passed name=None and watchlist_add was
INSERT OR IGNORE.

Three coordinated changes:

1. QuantDingerClient.get_symbol_name() hits the public
   GET /api/market/symbols/search endpoint (unauthed; seed DB lookup),
   returns the first result's name or None on any error / no match /
   symbol-echo. Best-effort, never raises.

2. Storage.watchlist_add now uses UPSERT with COALESCE(old, new) so:
   - existing name is never overwritten (preserves prior intent)
   - existing NULL name CAN be backfilled by a later add with a real
     name (matches the lazy-fill use case)
   added_by / added_at stay from the original insert.

3. cmd_watch awaits get_symbol_name before storing; passes the result
   through. Reply now echoes the name when available
   (e.g. "✅ 已加入 watchlist: 600519  貴州茅台").

Pre-existing watchlist rows with NULL name will stay NULL until
re-watched; users wanting to backfill can /unwatch + /watch the code.

Tests: +5 (1 storage backfill, 4 get_symbol_name covering happy /
no-match / symbol-echo / HTTP 500). Full suite 61/61.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants