

lemmy is really really cool.


lemmy is really really cool.


my goodness - I saw this pretty pretty long back.


Thanks - do give us a feedback :)


imo Swagger is good for looking at the API. For local and odd setups for example If you need shell scripts swagger becomes pretty rigid.


You can join our discord to meet people who are using it : https://discord.com/invite/XSYCf7JF4F


caffein rich whey protein.


the best possible answer.
but from a programmers perspective - shouldn’t it feel natural - you just keep filling up forms doing the same work again and again?
It means a lot of API tools feel like form-heavy tables where you just fill fields and hit send.
For example, testing CRUD often becomes multiple tabs, repeated headers/auth, and manual copy-paste of IDs.
they should not be forms for gods sake.


Everyone seems to hate this template.


Its an alternative to Monolithic Requests - Voiden has composable blocks which are an alternative to copy pasting entire request objects. We do not lock in collections in cloud like other api clients like postman and have a file centric and git native approach. Also we offer a unified toolchain - for design, testing, and documentation as an alternative to juggling multiple disconnected apps.


Well having decent documentation is kind of rare.


Thanks for this.


Thats pretty cool !


I posted this for womens day - a really really under rated person.
They do !
Here’s how to get started : https://docs.voiden.md/docs/getting-started-section/getting-started/openapi-imports
Unfortunately I agree but there are a few that are different, for example have you tried Voiden ( https://voiden.md/) maybe? We opensourced a few weeks back.
Postman was great when it made APIs simple, but over time all the accounts, cloud sync, and extra features kind of slowed down the core workflow. And then a lot of clients just ended up copying that model instead of rethinking it.
On the optimistic side we are seeing some stuff that want to rethink this: tools like Voiden and Yaak with a few new approaches like Git-native workflows, reusable request pieces, more composable setups basically making API work feel more like actual dev work again.
I am making a GitHub repository https://github.com/dp1620/awesome-markdown-devtools for markdown tools - I will include revealjs.com along with sli.dev