Repository navigation
External types? #81
Replies: 1 comment 3 replies
|
hey! fully agreed here. external lexicons were a miss in my initial implementation here and would be great to add. the simplest thing I can think of would be to have the cli support a command to pull in all external lexicons that are use. ideally, we detect which are used and then pull them into a folder like you mentioned " I've not made many complicated lexicons for my own uses yet. I'll be using external lexicons in the other thing I'm working on soon, but haven't reached that point quite yet. prototypey kinda came from me wanting to try the idea of fully inferring types from lexicon definitions and i'm only now starting to be a user of it more. |
Uh oh!
There was an error while loading. Please reload this page.
Hey @tylersayshi , I'm really enjoying what prototypey is doing so I'm experimenting with it on a bigger atproto project I'm building 😊
How do you see external lexicons as canonically fitting in here? eg. if my lexicon uses a
com.atproto.strongRef, should I keep a prototypey copy of that lexicon in my typescript? Should I keep the JSON inlexicons/com/atproto/strongRef.jsonand usefromJSONin my code to be able to reference them? Something else?I'm wondering if you've made more use of lexicons since you built prototypey, and if you've found ways that work well for you with external lexicons 😊 Using external lexicons is such a powerful part of atproto, I feel like there's huge value in it being as easy to use as the type inference you have for local references!
All reactions