core/api/tangled/ at e52b67e89797be85491c7b0b8488f10ba3ccf180 · dunkirk.sh/core · Tangled

dunkirk.sh / core

forked from tangled.org/core

0

This repository has no description

0

core / api / tangled /

at e52b67e89797be85491c7b0b8488f10ba3ccf180 17 files

Anirudh Oppiliappan appview: refactor lexicon setup and simplify 1y ago

appview: refactor lexicon setup and simplify Can't use sh.tangled.repo.pull.state.{open,closed,merged} since that results in a stateopen.go -- overwriting issue.state.open etc. Hence, it's pull.status.

1 year ago

add stars to tangled

1 year ago

add /follow endpoint

1 year ago

issuecomment.go

lexicons: issue, issue state and comment Custom lexicon for issues, issue state (open, closed) and issue comments. The case with issue_at is a bit weird since we have a circular dependency: the issue record requires the issue_id, and the issue entry in the db requires the issue_at. To resolve this we write to the db without the issue_at, fetch the issue_id, create the issue record on the PDS, and then update the issue_at (with SetIssueAt). It's not great, but whatever.

1 year ago

lexicons: issue, issue state and comment Custom lexicon for issues, issue state (open, closed) and issue comments. The case with issue_at is a bit weird since we have a circular dependency: the issue record requires the issue_id, and the issue entry in the db requires the issue_at. To resolve this we write to the db without the issue_at, fetch the issue_id, create the issue record on the PDS, and then update the issue_at (with SetIssueAt). It's not great, but whatever.

1 year ago

add server policies through the firehose

1 year ago

appview: refactor lexicon setup and simplify Can't use sh.tangled.repo.pull.state.{open,closed,merged} since that results in a stateopen.go -- overwriting issue.state.open etc. Hence, it's pull.status.

1 year ago

appview: refactor lexicon setup and simplify Can't use sh.tangled.repo.pull.state.{open,closed,merged} since that results in a stateopen.go -- overwriting issue.state.open etc. Hence, it's pull.status.

1 year ago

lexicons: issue, issue state and comment Custom lexicon for issues, issue state (open, closed) and issue comments. The case with issue_at is a bit weird since we have a circular dependency: the issue record requires the issue_id, and the issue entry in the db requires the issue_at. To resolve this we write to the db without the issue_at, fetch the issue_id, create the issue record on the PDS, and then update the issue_at (with SetIssueAt). It's not great, but whatever.

1 year ago

appview: refactor lexicon setup and simplify Can't use sh.tangled.repo.pull.state.{open,closed,merged} since that results in a stateopen.go -- overwriting issue.state.open etc. Hence, it's pull.status.

1 year ago

appview: refactor lexicon setup and simplify Can't use sh.tangled.repo.pull.state.{open,closed,merged} since that results in a stateopen.go -- overwriting issue.state.open etc. Hence, it's pull.status.

1 year ago

appview: refactor lexicon setup and simplify Can't use sh.tangled.repo.pull.state.{open,closed,merged} since that results in a stateopen.go -- overwriting issue.state.open etc. Hence, it's pull.status.

1 year ago

statusclosed.go

appview: refactor lexicon setup and simplify Can't use sh.tangled.repo.pull.state.{open,closed,merged} since that results in a stateopen.go -- overwriting issue.state.open etc. Hence, it's pull.status.

1 year ago

statusmerged.go

appview: refactor lexicon setup and simplify Can't use sh.tangled.repo.pull.state.{open,closed,merged} since that results in a stateopen.go -- overwriting issue.state.open etc. Hence, it's pull.status.

1 year ago

appview: refactor lexicon setup and simplify Can't use sh.tangled.repo.pull.state.{open,closed,merged} since that results in a stateopen.go -- overwriting issue.state.open etc. Hence, it's pull.status.

1 year ago

tangledpublicKey.go

rename to tangled

1 year ago

mvp: edit repo descriptions - implemented in a backwards compatible way, introduces migrations and updates an existing lexicon - newly added field is not marked required, so we should still be able to index old repo-create events properly

1 year ago