Monorepo for Tangled โ€” https://tangled.org

appview/pages: markup: add @ user-mention parsing in markdown #736

merged
opened by boltless.me targeting master from feat/mentions
0
by boltless.me 0 comments
expand 1 commit
appview/pages: markup: add @ user-mention parsing in markdown
1
by boltless.me 0 comments
expand 1 commit
appview/pages: markup: add @ user-mention parsing in markdown
2
by boltless.me 0 comments
expand 1 commit
appview/pages: markup: add @ user-mention parsing in markdown
3
by boltless.me 0 comments
expand 1 commit
appview/pages: markup: add @ user-mention parsing in markdown
4
by boltless.me 0 comments
expand 1 commit
appview/pages: markup: add @ user-mention parsing in markdown
5
by boltless.me 2 comments
expand 1 commit
appview/pages: markup: add @ user-mention parsing in markdown

this class seems to not be used (it does not render as text-red-500 for me atleast?), is this intentional?

in any case, i think the current styles for the mention (styled as a a tag) look good. github's style for mentions would be cool too (bold without underline, but still linked).

ah forgot to remove that test code. resubmitting with style update! (following github style and match with current user handle styles)

sign up or login to add to the discussion
6
by boltless.me 0 comments
expand 1 commit
appview/pages: markup: add @ user-mention parsing in markdown
7
by boltless.me 0 comments
expand 1 commit
appview/pages: markup: add @ user-mention parsing in markdown
8
by boltless.me 1 comment
expand 1 commit
appview/pages: markup: add @ user-mention parsing in markdown

We will likely add more extensions to the markdown renderer in the future (one immediate example is callouts, which I plan to fork and modify in-tree). Maybe we can have an extensions subpackage under the markdown package?

And maybe rename the markdown_at_extension.go to just atlink.go?

sign up or login to add to the discussion
9
by boltless.me 2 comments
expand 1 commit
appview/pages: markup: add @ user-mention parsing in markdown

@anirudh.fi I moved it to markup/extension/atlink.go. does this seem good? I originally named it that way because I thought we will introduce non-markdown renderers in future. So, considering we already have markup/markdown.go, markup/markdown_sthsth.go seems reasonable. Maybe it was bit too early.

Ah, I see. I appreciate the rationale, but we wonโ€™t support non-markdown renderers for comments/issues/other text bodies that arenโ€™t the readme itself. Once we do support other renderers. we can subpackage this under โ€˜markdownโ€™.

sign up or login to add to the discussion
10
by boltless.me 1 comment
expand 1 commit
appview/pages: markup: add @ user-mention parsing in markdown
11
by boltless.me 0 comments
expand 1 commit
appview/pages: markup: add @ user-mention parsing in markdown
12
by boltless.me 0 comments
expand 1 commit
appview/pages: markup: add @ user-mention parsing in markdown
13
by boltless.me 0 comments
expand 1 commit
appview/pages: markup: add @ user-mention parsing in markdown
Labels

None yet.

assignee

None yet.

Participants 3
AT URI
at://did:plc:xasnlahkri4ewmbuzly2rlc5/sh.tangled.repo.pull/3m4jbido5pa22