Fix optional vector serialization in ReplyParameters #11
+14
−3
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.
Issue #6 identified that optional vector fields like
ReplyParameters.quoteEntitieswere always serialized as empty arrays[]when unset, violating Telegram Bot API spec which requires omitting unset optional fields entirely.Changes
ReplyParameters.quoteEntitiesinstd::optional<std::vector<MessageEntity::Ptr>>std::optional<std::vector<T>>that skips serialization when empty, serializes vector (including empty[]) when setBehavior
This pattern applies to all optional vector fields and prevents API errors from sending unnecessary default values.
Warning
Firewall rules blocked me from connecting to one or more addresses (expand for details)
I tried to connect to the following addresses, but was blocked by firewall rules:
esm.ubuntu.com/usr/lib/apt/methods/https /usr/lib/apt/methods/https(dns block)If you need me to access, download, or install something from one of these locations, you can either:
Original prompt
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.