![](https://lemmy.fmhy.ml/pictrs/image/439f9e09-acfc-42da-84a0-21d7795b0c04.png)
![](https://lemmy.ml/pictrs/image/1f910de9-62b5-43a9-8c93-94821c945577.png)
Yep… and if you and I got discouraged, how many other developers did as well? This is why good docs are essential for a healthy ecosystem.
Yep… and if you and I got discouraged, how many other developers did as well? This is why good docs are essential for a healthy ecosystem.
No, I was just chewing on various ideas to integrate with Lemmy and was disappointed with the docs I saw. They seemed OK-ish if you wanted to use the JS client, but not great if you want to do something else.
On similar projects, I’m used to seeing OpenAPI/Swagger/etc. where you have docs on the incoming bodies/fields, what values they can contain, etc.
Right now it’s really bare bones. I see things like ‘auth’ OPTIONAL but not really sure what would go in there.
I can RTFS like another poster said, but of course that’s not as convenient as “general purpose” API docs with examples / tutorial.
I was curious to see if the reply was going to be:
OR
Because MONEY and lack of choice in some markets… easy.
Your experience mirrors mine, where you must refer to the Rust and/or JS code to have a chance in hell.