←back to thread

49 points emykhailenko | 1 comments | | HN request time: 0s | source
Show context
dhruvkb ◴[] No.43111614[source]
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

replies(2): >>43112412 #>>43114525 #
edweis ◴[] No.43112412[source]
Referring to OpenAPI: https://github.com/OAI/OpenAPI-Specification
replies(1): >>43112913 #
t1mmen ◴[] No.43112913[source]
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!

replies(1): >>43114408 #
1. emykhailenko ◴[] No.43114408[source]
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.