fix(gateway): add missing config.yaml mapping for telegram reply_to_mode - #17183
Closed
hash7in wants to merge 1 commit into
Closed
fix(gateway): add missing config.yaml mapping for telegram reply_to_mode#17183hash7in wants to merge 1 commit into
hash7in wants to merge 1 commit into
Conversation
telegram.reply_to_mode in config.yaml was silently ignored because _build_gateway_config() never mapped it to PlatformConfig. Only the TELEGRAM_REPLY_TO_MODE env var worked. This adds the missing mapping, following the same pattern as disable_link_previews.
Collaborator
Contributor
|
Thanks for the focused config fix. This is an automated hermes-sweeper review; the requested behavior is already implemented on current
|
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
in config.yaml is silently ignored. Only env var works because never maps the yaml value to .
Other telegram-specific settings like already have this mapping — was just missed.
Fix
6 lines, same pattern as . Env var takes precedence when both are set.