use com.atproto.repo.strongRef for more explicit reference &
markup#markdown type to give clear semantic meaning in markdown
Close: https://tangled.org/tangled.org/core/issues/383 Signed-off-by: Seongmin Lee git@boltless.me
com.atproto.repo.strongRef and sh.tangled.markup#markdown
#1271
use com.atproto.repo.strongRef for more explicit reference &
markup#markdown type to give clear semantic meaning in markdown
Close: https://tangled.org/tangled.org/core/issues/383 Signed-off-by: Seongmin Lee git@boltless.me
aturi->reactionMap from DB
CommentList out of Issue
IssueComment to Comment
PullComment to Comment
com.atproto.repo.strongRef and sh.tangled.markup#markdown
sh.tangled.comment lexicon
This is a binary file and will not be displayed.
This is a binary file and will not be displayed.
This is a binary file and will not be displayed.
This is a binary file and will not be displayed.
com.atproto.repo.strongRef and sh.tangled.markup.markdown
use `com.atproto.repo.strongRef` for more explicit reference &
`markup.markdown` type to give clear semantic meaning in markdown
Close: <https://tangled.org/tangled.org/core/issues/383>
Signed-off-by: Seongmin Lee <git@boltless.me>
com.atproto.repo.strongRef and sh.tangled.markup.markdown
use `com.atproto.repo.strongRef` for more explicit reference &
`markup.markdown` type to give clear semantic meaning in markdown
Close: <https://tangled.org/tangled.org/core/issues/383>
Signed-off-by: Seongmin Lee <git@boltless.me>
com.atproto.repo.strongRef and sh.tangled.markup.markdown
use `com.atproto.repo.strongRef` for more explicit reference &
`markup.markdown` type to give clear semantic meaning in markdown
Close: <https://tangled.org/tangled.org/core/issues/383>
Signed-off-by: Seongmin Lee <git@boltless.me>
com.atproto.repo.strongRef and sh.tangled.markup.markdown
use `com.atproto.repo.strongRef` for more explicit reference &
`markup.markdown` type to give clear semantic meaning in markdown
Close: <https://tangled.org/tangled.org/core/issues/383>
Signed-off-by: Seongmin Lee <git@boltless.me>
com.atproto.repo.strongRef and sh.tangled.markup.markdown
use `com.atproto.repo.strongRef` for more explicit reference &
`markup.markdown` type to give clear semantic meaning in markdown
Close: <https://tangled.org/tangled.org/core/issues/383>
Signed-off-by: Seongmin Lee <git@boltless.me>
com.atproto.repo.strongRef and sh.tangled.markup.markdown
use `com.atproto.repo.strongRef` for more explicit reference &
`markup.markdown` type to give clear semantic meaning in markdown
Close: <https://tangled.org/tangled.org/core/issues/383>
Signed-off-by: Seongmin Lee <git@boltless.me>
com.atproto.repo.strongRef and sh.tangled.markup.markdown
use `com.atproto.repo.strongRef` for more explicit reference &
`markup.markdown` type to give clear semantic meaning in markdown
Close: <https://tangled.org/tangled.org/core/issues/383>
Signed-off-by: Seongmin Lee <git@boltless.me>
com.atproto.repo.strongRef and sh.tangled.markup#markdown
use `com.atproto.repo.strongRef` for more explicit reference &
`markup#markdown` type to give clear semantic meaning in markdown
Close: <https://tangled.org/tangled.org/core/issues/383>
Signed-off-by: Seongmin Lee <git@boltless.me>
com.atproto.repo.strongRef and sh.tangled.markup#markdown
use `com.atproto.repo.strongRef` for more explicit reference &
`markup#markdown` type to give clear semantic meaning in markdown
Close: <https://tangled.org/tangled.org/core/issues/383>
Signed-off-by: Seongmin Lee <git@boltless.me>
lexicons/comment/comment.json:36what about round 0