Signed-off-by: Seongmin Lee git@boltless.me
draft: render backlinks #765
STACK 4
expand 1 commit
hide 1 commit
Signed-off-by: Seongmin Lee <git@boltless.me>
expand 1 commit
hide 1 commit
Signed-off-by: Seongmin Lee <git@boltless.me>
expand 1 commit
hide 1 commit
Signed-off-by: Seongmin Lee <git@boltless.me>
expand 1 commit
hide 1 commit
Signed-off-by: Seongmin Lee <git@boltless.me>
expand 1 commit
hide 1 commit
Signed-off-by: Seongmin Lee <git@boltless.me>
expand 1 commit
hide 1 commit
Signed-off-by: Seongmin Lee <git@boltless.me>
expand 1 commit
hide 1 commit
Signed-off-by: Seongmin Lee <git@boltless.me>
expand 1 commit
hide 1 commit
currently all backlinks are parsed with markdown parser.
So only explict urls like below are supported:
- <https://tangled.org/owner.com/repo-name/issues/123>
- [full url](https://tangled.org/owner.com/repo-name/issues/123)
- [absolute path](/owner.com/repo-name/issues/123)
Also `#comment-123` fragment is supported too.
All references in issue/pull/comment records are stored in at-uri
format. we do have a `mentions` field, but it isn't used yet. mentions
are parsed on rendering and aren't stored anywhere for now.
Signed-off-by: Seongmin Lee <git@boltless.me>
expand 1 commit
hide 1 commit
currently all backlinks are parsed with markdown parser.
So only explict urls like below are supported:
- <https://tangled.org/owner.com/repo-name/issues/123>
- [full url](https://tangled.org/owner.com/repo-name/issues/123)
- [absolute path](/owner.com/repo-name/issues/123)
Also `#comment-123` fragment is supported too.
All references in issue/pull/comment records are stored in at-uri
format. we do have a `mentions` field, but it isn't used yet. mentions
are parsed on rendering and aren't stored anywhere for now.
Signed-off-by: Seongmin Lee <git@boltless.me>
expand 1 commit
hide 1 commit
currently all backlinks are parsed with markdown parser.
So only explict urls like below are supported:
- <https://tangled.org/owner.com/repo-name/issues/123>
- [full url](https://tangled.org/owner.com/repo-name/issues/123)
- [absolute path](/owner.com/repo-name/issues/123)
Also `#comment-123` fragment is supported too.
All references in issue/pull/comment records are stored in at-uri
format. we do have a `mentions` field, but it isn't used yet. mentions
are parsed on rendering and aren't stored anywhere for now.
Signed-off-by: Seongmin Lee <git@boltless.me>
expand 1 commit
hide 1 commit
currently all backlinks are parsed with markdown parser.
So only explict urls like below are supported:
- <https://tangled.org/owner.com/repo-name/issues/123>
- [full url](https://tangled.org/owner.com/repo-name/issues/123)
- [absolute path](/owner.com/repo-name/issues/123)
Also `#comment-123` fragment is supported too.
All references in issue/pull/comment records are stored in at-uri
format. we do have a `mentions` field, but it isn't used yet. mentions
are parsed on rendering and aren't stored anywhere for now.
Signed-off-by: Seongmin Lee <git@boltless.me>
expand 1 commit
hide 1 commit
currently all backlinks are parsed with markdown parser.
So only explict urls like below are supported:
- <https://tangled.org/owner.com/repo-name/issues/123>
- [full url](https://tangled.org/owner.com/repo-name/issues/123)
- [absolute path](/owner.com/repo-name/issues/123)
Also `#comment-123` fragment is supported too.
All references in issue/pull/comment records are stored in at-uri
format. we do have a `mentions` field, but it isn't used yet. mentions
are parsed on rendering and aren't stored anywhere for now.
Signed-off-by: Seongmin Lee <git@boltless.me>
tested this locally: and all edge cases i can think of are handled pretty well! the rendering of backlinks also looks good. thanks for the brilliant work on this!