-
-
Notifications
You must be signed in to change notification settings - Fork 7.3k
Description
The problem
Atproto is growing in popularity for good reason, its a very nice way to unify applications.
This can be done by declaring a lexicon which defines data formats and endpoints in a structured way that can be integrated with atproto. https://atproto.com/specs/lexicon
This will be using the data from an openapi.json file but i couldn't find a tool for generating a lexicon from an openid files.
The Solution
A tool that generates a lexicon definition file from an openapi.json spec , the developer can then edit it down to just the functions and types they want to use on atproto and then publish it in the specific location on their site.
Alternatives
I have considered doing this myself but i'm not so familiar with OpenAPI internals and figured that for someone who is used to this it would reasonably simple.
I am happy to help with making this happen and finding ways to test it. I think this will be something quite a few people will use because atproto is growing massively.