-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support attachments with title, test and author #18
Conversation
No longer need to parse block quotes ourselves.
The only difference between the fork and upstream slackdown is multiline code blocks, i.e. triple backticks: ```something```. The markdown parser we're now using already has support for this.
The title is now linked.
da8eac9
to
34c159b
Compare
I can't figure out why this was even being done. I can't find anything in the spec about edits in replies needing a fallback. Element doesn't do it either, if it's good for Element, must be good for us.
Just the failing test is prevening this from being merged, @psrpinto is working on fixing it. |
An interesting sideeffect of this is when you write Markdown on Slack, it will render as formatted on Matrix when bridged. (You can press cmd-shift-f in Slack to achieve formatting there) Remark: attachments in Slack are deprecated and the Block Kit should be used, we still need to add support for that. |
Wow, case-insensitive vs case-sensitive filesystem! |
Yep, noticed it by chance, turns out it was the issue. Merging. |
This PR improves rendering of slack attachments. Not all fields are supported (e.g. images), but the most common ones should be.
This PR also includes some further refactors, and also fixes an issue that caused edits in threads to be posted as replies (upstream issue).
Additionally, we're now using a markdown parser, which simplifies a lot of things (e.g. don't need to parse blockquotes ourselves).
Screen captures
On Matrix
On Matrix, before this PR
On Slack