tangled.org / core
Monorepo for Tangled tangled.org
fork atom

appview/notify: merge new comment events into one #867

open
opened by boltless.me targeting master from sl/wnrvrwyvrlzo
STACK 4
#867 appview/notify: merge new comment events into one
3/3
0
#2
#866 appview: replace IssueComment to Comment
2/3
0
#2
#865 appview: replace PullComment to Comment
2/3
0
#2
#864 lexicons: add general sh.tangled.comment lexicon
3/3
0
#2
0
by boltless.me 3 comments
expand 1 commit
1a41a366
appview/notify: merge new comment events into one
boltless.me

note: I'm choosing sh.tangled.comment NSID here. Tell me if we would prefer something else like sh.tangled.feed.comment

anirudh.fi

I think sh.tangled.comment is fine, but more importantly, are we still sticking to sh.tangled or does it make sense to move this to the org.tangled namespace? Assuming we're moving everything eventually. cc @oppi.li

boltless.me

I think we should stick on sh.tangled for now as there can be large amounts of changes from PR refactor / did-for-repo. We can consider moving entire collections to org.tangled once tangled lexicons become more stable.

build.yml
fmt.yml
test.yml
sign up or login to add to the discussion
1
by boltless.me 1 comment
expand 1 commit
08c1258b
appview/notify: merge new comment events into one
build.yml
fmt.yml
test.yml
sign up or login to add to the discussion
2
by boltless.me 0 comments
expand 1 commit
d6eaecd5
appview/notify: merge new comment events into one
build.yml
fmt.yml
test.yml
merge conflicts detected
sign up or login to add to the discussion
Labels

None yet.

assignee

None yet.

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