Naoki Kanatani
Naoki Kanatani
@mhemken-nyt Hi, I fixed this PR in documentation/events-example branch. Could you add these fixes in this PR? git diff ```diff diff --git a/examples/eventsapi/README.md b/examples/eventsapi/README.md index 9b4e27d..af8b701 100644 --- a/examples/eventsapi/README.md +++...
Thanks for reporting! I think whether we should use pretty print or not is one thing, whether we should use application/json or not is another. What problem do you resolve?...
I'm sorry. I'm not sure about your use case. Which JSON do you want to have prettty-printed output?(Is it the body of an HTTP request sent to Slack?)
> Yes, it's the body (actual message displayed to the user on slack) of the HTTP request I want to pretty print. I understood! Thanks.
Thank you for reporting. I'll confirm later.
In this case, you can parse correctly if you fix your snippets like below. ```go // before L14 parsed := slack.ContextBlock{} // after L 14 var parsed *slack.ContextBlock ``` I...
If we change the receiver type to a value instead of a pointer, I believe this change may be applied to all `XxxBlock` types. This is to avoid misuse.
@zchee What do you think?
Thank you for your reporting! Let me give some consideration to how to fix.
Thanks! According to Slack support, this behaviour seems to be a bug in Slack API. So I'd like to keep page-based pagination, but make the change to support cursor-based pagination...