Skip to content
This repository has been archived by the owner on Mar 11, 2024. It is now read-only.

Use SendMessageV2 everywhere #116

Merged
merged 1 commit into from
Sep 30, 2019

Conversation

toolateforteddy
Copy link
Contributor

This isn't necessary everywhere, but for standardization, I thought
it would be good to really deprecate SendMessageV1.

The place this IS needed is in PeriodicCommands v2 and PassiveCommands
V2. In both those places, objects come back from the caller with ProtoParams
that should be forwarded through to the message sending.

@coveralls
Copy link

coveralls commented Sep 28, 2019

Coverage Status

Coverage increased (+0.3%) to 97.248% when pulling fcc799f on toolateforteddy:useSendV2Everywhere into 51bcba0 on go-chat-bot:master.

Then rename SendMessageV2 to SendMessage because it does the same thing.
This is a breaking change, but it is an easy one to fix, so I want to do
it anyway.

This isn't necessary everywhere, but for standardization, I thought
it would be good to really deprecate SendMessageV1.

The place this IS needed is in PeriodicCommands v2 and PassiveCommands
V2. In both those places, objects come back from the caller with ProtoParams
that should be forwarded through to the message sending.
@fabioxgn
Copy link
Member

@toolateforteddy I agree with deprecated V1. Thanks for the PR.

@fabioxgn fabioxgn merged commit 9254c8e into go-chat-bot:master Sep 30, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants