dan @danabra.mov@bsky.brid.gy
Public

ok jesus i guess claude finally explained it to me: "To publish it, you literally just add $type" i did not see that connection at all because i thought `com.atproto.lexicon.schema` describes some metadata format i'm not familiar with and i'm supposed to guess how to embed lexicons in it

wait but my lexicons live in my lexicons/folder as *.jsonfiles. are you saying i need to transform each and stuff it into an object with some metadaa?02:14Clarified minimal transformation needed for lexicon files.The user is asking about the relationship between their local lexicon JSON files (which they have in a lexicons/ folder) and publishing them as atproto records. Looking at the original docs, it says: "In practice, same fields as Lexicon Files should be included, along with $type." So lexicon files already have: lexicon: 1 id: the NSID defs: the definitions To publish them as records, you just need to add $type: "com.atproto.lexicon.schema". So the transformation is minimal - you're basically just adding the $type field to your existing lexicon JSON files. Let me clarify this for the user.Oh no, it's way simpler than that. Your lexicon files already have almost everything they need. Your lexicons/com/alice/bookmarks/bookmark.json probably looks like: json{ "lexicon": 1, "id": "com.alice.bookmarks.bookmark", "defs": { "main": { "type": "record", ... } } } To publish it, you literally just add $type: json{ "$type": "com.atproto.lexicon.schema",
0
0
0

If you have a fediverse account, you can quote this note from your own instance. Search https://bsky.brid.gy/convert/ap/at://did:plc:fpruhuo22xkm5o7ttr2ktxdo/app.bsky.feed.post/3maoaxblkhs2n on your instance and quote it. (Note that quoting is not supported in Mastodon.)