We need the AST from inside InnerTextMessage in order to determine whether the Markdown has any "pressables" (link or spoiler for now, but @mention in the future).
Details
Details
Flow, tested with following diff
Diff Detail
Diff Detail
- Repository
- rCOMM Comm
- Lint
No Lint Coverage - Unit
No Test Coverage
Event Timeline
| native/chat/text-message-markdown-context.js | ||
|---|---|---|
| 17 | Prettier seems to force this long line unfortunately | |
Comment Actions
Setting up the parser seems consistent with the existing markdown code - I assume TextMessageMarkdownContext will replace MessageContext from D5515? I.e. MarkdownSpoiler will rebase these changes and then retrieve the messageKey from this instead