You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently session.ChannelMessages() accepts before and after message IDs as strings. Everywhere else message IDs are strings, so to pass them to ChannelMessages() one has to call strconv.Atoi() or something similar, which is rather cumbersome.
Consider making ChannelMessages accept Message ID as a string instead.
One caveat is that this change will make it difficult to obtain the very last message (channel.LastMessageId), because ChannelMessages does not include first and last messages in the response. A workaround to that would be making utility functions to return an Message ID that immediately follows/precedes given one.
Currently
session.ChannelMessages()
acceptsbefore
andafter
message IDs as strings. Everywhere else message IDs are strings, so to pass them toChannelMessages()
one has to callstrconv.Atoi()
or something similar, which is rather cumbersome.Consider making
ChannelMessages
accept Message ID as astring
instead.One caveat is that this change will make it difficult to obtain the very last message (
channel.LastMessageId
), becauseChannelMessages
does not include first and last messages in the response. A workaround to that would be making utility functions to return an Message ID that immediately follows/precedes given one.or something along the lines.
The text was updated successfully, but these errors were encountered: