Repository navigation
Conversation
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.
Problem
tg invite id:<n> @example_userrejects the ID even aftertg chats listhas cached the peer. The invitee uses the CLI's ID-aware resolver, but the
destination previously went straight to the username/link/phone resolver.
This leaves groups without a public username without a numeric target.
Fix
id:<n>destinations through the selected account's existingpeer cache. Reject a raw ID that matches multiple cached peer types rather
than guessing the destination. Username and link resolution are unchanged.
ok: trueafter a partial or unsuccessful invite. Telegram still enforcespermissions and privacy rules.
tg invite --help.Verification
The mocked regression tests cover private basic groups and supergroups,
the existing username path, uncached and ambiguous IDs, and skipped
invitees. No live sessions or real peer data were used.
go test -race ./...go mod tidy -diff