| ▲ | dhruvkb 2 days ago |
| I'm currently using Bruno, which uses its own format "Bru Lang" for storing HTTP requests as plain text[1]. The VS Code extension is great but I'd much prefer the standard backed by 30k+ stars was extended instead of a new format to introduce fragmentation in this space. [1]: https://docs.usebruno.com/bru-lang/overview |
|
| ▲ | edweis 2 days ago | parent | next [-] |
| Referring to OpenAPI: https://github.com/OAI/OpenAPI-Specification |
| |
| ▲ | t1mmen 2 days ago | parent [-] | | 100%, this. Im a bit flabbergasted I haven’t yet found a HTTP/API client that simply runs off an oAPI spec. Sure, most support «import of..», but do any support oAPI’s as continuously evolving source of truth? Our oAPI spec is auto-generated (based off ts-rest.com contracts), and I’d love one that understands this, including auto-refreshing/importing of spec when it changes on disk. If anyone knows of this magical piece of software, please share! | | |
| ▲ | emykhailenko 2 days ago | parent [-] | | Thank you all for showing interest in this project. You described exactly what motivated me to create this language – support for OpenAPI specs. I just wanted to have a language where I could import an OpenAPI spec and leverage the intelligence, because, like you, in all my projects the specs were autogenerated. |
|
|
|
| ▲ | emykhailenko 2 days ago | parent | prev [-] |
| Yeah, I agree. Bruno is a great tool, but it's missing one key component that I needed (maybe it's just me) – it can't run multiple requests in a chain. Also, constructions like:
get {
url: ....
}
feel too verbose to me, I wanted something clearer, like:
get /users
;)
But in general, thank you guys for your interest, my goal is to gain that 30k+ starts ))) |
