Rustam
Rustam
Possibly duplicate of #205
@raine that is a very elegant solution, thank you for sharing!
Hey Axel, that's very interesting, it looks like the upstream may not have an appropriate struct tags. Is this just some rich text? How can I reproduce this?
NVM, was able to reproduce ```{"channel_id":"CHY5HUESG","name":"everyone","messages":[{"client_msg_id":"79675403-4659-4828-a8ac-af4f16bca2d6","type":"message","user":"UHSD97ZA5","text":"Hello\n```preformatted?```\ntest","ts":"1688031487.552909","team":"THY5HTZ8U","replace_original":false,"delete_original":false,"metadata":{"event_type":"","event_payload":null},"blocks":[{"type":"rich_text","block_id":"Ixznh","elements":[{"type":"rich_text_section","elements":[{"type":"text","text":"Hello\n"}]},{"Type":"rich_text_preformatted","Raw":"{\"Type\":\"rich_text_preformatted\",\"Raw\":\"{\\\"type\\\":\\\"rich_text_preformatted\\\",\\\"elements\\\":[{\\\"type\\\":\\\"text\\\",\\\"text\\\":\\\"preformatted?\\\"}],\\\"border\\\":0}\"}"},{"type":"rich_text_section","elements":[{"type":"text","text":"test"}]}]}]}]} ```
Looks like it's not implemented in the upstream, that's why it just dumps the block into the "RAW" section. The corresponding RAW API output looks like the following (without any...
There's no implementation for the RichTextElement, and it falls back to [this](https://github.com/slack-go/slack/blob/master/block_rich_text.go#L86-L89) ``` type RichTextUnknown struct { Type RichTextElementType Raw string } ``` There's no tags on this struct, therefore...
Cool, thanks for raising this, I wasn't aware. Yes, there's a bunch of them, and "rich_text_list" in particular is this one: https://github.com/slack-go/slack/pull/1155 waiting for the time to come for someone...
Submitted the PR to slack repo to add rich_text_quote and rich_text_preformatted https://github.com/slack-go/slack/pull/1260, the rich_text_list was merged yesterday.
Hey @svenssonaxel, good news, this change was merged upstream, and i just updated the master, will be available in next patch.
Hi @aijkl, thank you for the suggestion, I think i got the idea. There will be a resume logic implemented soon-ish (as described here #174), can probably accommodate for the...