![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://programming.dev/pictrs/image/8140dda6-9512-4297-ac17-d303638c90a6.png)
Looks like the best openapi front. I looked into using it, but it didn’t seem free. Too bad this one is outdated. Lemmys API has changed quiet a bit since then.
Looks like the best openapi front. I looked into using it, but it didn’t seem free. Too bad this one is outdated. Lemmys API has changed quiet a bit since then.
(Author btw)
Can you expand on this? This was written for Kotlin usage. It automates generating API based on this spec.
I have no idea what you mean with ‘using other approaches to calling the endpoints’
Lemmy has only one API. It’s same API used for lemmy-ui.
This is just a “better” documentation for it.
The API works for for cloudfare instances too.
There is also a swagger ui variant
I genuinely don’t understand how there can be so many languages and all of them be painful to use
What about kotlin?
Test missing comment please ignore
Yeah KBIN is getting the fundamentals right and at a pretty fast pace. I just don’t like their nomenclature and techstack. It’s also trying to be twitter and reddit at the same time.
Lemmy actually uses it own API, so you would think they would have documentation as a priority. Lemmy gets funded by NLnet (so is KBIN) and they get paid by each released feature. I think they focused too much on adding features, and this feature creep caused big performance issues. Aggregation is still big performance hog that causes instability which probably the biggest problem rn with Lemmy. They also wasted lots of resources into things that don’t scale like the AsyncApi. Before they got hit by the reddit migration, they were even thinking of doing 1.0.0 release, that woulda complicated a lot of things. It’s good that the migration happened, it shook Lemmy devs, probably would have been better if it happened earlier though.
Their approach requires no additional work as it’s fully automated. That’s the biggest reason.
I wrote the routes manually which took some time. And it still needs quite some work for the summaries and descriptions
use the jwt to call /site, the person subsection has the id. That’s how Jerboa does it
I do not see how critisms for the JS API docs are relevant for my openapi documentation.
This documentation aims to solve all those problems in a language agnostic way. It descibes the endpoints, the request object, the status, the response object, the authentication needed in visual/text. It allows you test it right from the browser, allows you to copy a working curl command, search for endpoints based on keywords, allows you to import the entire spec into postman/alts.
I ve never had any problems with CF instances but I mostly test with voyager.lemmy.ml