Turns out that ReceivedMessage::DeliveryDetails::error provides more specific error messages than ReceivedMessage::DeliveryDetails::dbusError
Hence, the error messages in ChannelTextSendError must be included in the list of error strings in the telepathy-spec so that ReceivedMessage::DeliveryDetails::dbusError provides specific error messages
Adjusting summary a bit.
The general principle is that whenever we emit an (enum member, string error name) pair, the string error name is meant to be at least as specific as the enum member.
In this case, we can't (always) do that, because, for instance, there is no D-Bus error name that corresponds to "message too long":
20:13 < shadeslayer> It's just that ReceivedMessage::DeliveryDetail::error is
giving me ChannelTextSendErrorTooLong whereas
ReceivedMessage::DeliveryDetails::dbusError gives me
org.freedesktop.Telepathy.Error.InvalidArgument for the
exact same error
patches welcome, but not a spec 1.0 blocker
-- GitLab Migration Automatic Message --
This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.
You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/telepathy/telepathy-spec/issues/136.