tangled.org / core
Monorepo for Tangled — https://tangled.org
fork atom

sh.tangled.knot.version -> sh.tangled.knot.describeKnot #327

open
opened by boltless.me

descibeKnot can be used for more flexible use-cases.

For example, knot can show its git endpoints here.

{
  "version": "1.11.0-alpha",
  "gitEndpoints": [
    "user@knot.example.com",
    "ssh://user@knot.example.com:1234",
    "https://knot.example.com"
  ]
}
anirudh.fi

Perhaps getInfo or something similar? I still think a basic version endpoint is of value, however.

boltless.me (author)

I'm following the nsid com.atproto.server.describeServer here which is used to fetch the capability of PDS. sh.tangled.knot.version (and many other tangled lexicons) is not following nsid guidelines.

anirudh.fi

Okay, that's good precedent in that case. And yes, we aren't following NSID guidelines in a good chunk of our lexicon—we should fix this before getting out of alpha.

This sounds good to me then.

sign up or login to add to the discussion
Labels

None yet.

area
knot
assignee
boltless.me
Participants 2
AT URI
at://did:plc:xasnlahkri4ewmbuzly2rlc5/sh.tangled.repo.issue/3m7q2xmg2vh22