Naoki Kanatani
Naoki Kanatani
@storz Sorry for slow response. Umm, I think the former looks better for now The latter is fine, but I thought it might cause some confusion because some of APIs...
Thanks. I have one concern, so please be patient...
@naormatania When I tried it, I came across strange behavior. Slack documentation says that the `service_id` field is string, but actual response's one is not string but int... So slack-go/slack...
Sorry for delay. According to support, this is documentation's mistake.
@naormatania I confirmed support again. According to support's response, the type of `service_id` is only integer, so we do not seem to need to consider the string type. :sob:
@naormatania thanks! I found a new undocumented behavior... It seems that the `user_id` can be 0 (= a number) like following example. ```json { "user_id": 0, "user_name": "slack", "date": "1595673313",...
@Yohan460 Thanks for submitting PR! This PR has backward-incompatibility changes. So we'll release this in the next minor version(= v.10.0) if approved.
@Yohan460 It seems that the lint phase in CI failed, so please confirm it.
Could you run `gofmt -w conversation.go`?
Ah, sorry. My understanding was wrong. By the way, this problem can also occur with `BlockAction` 🤔 I think it would be desirable to have a solution that prevents this...