• jtrek@startrek.website
    link
    fedilink
    arrow-up
    2
    ·
    2 hours ago

    I started using bruno for lazy gui “make a request” needs.

    But for anything serious python requests is right there, so I mostly used that for testing.

    • onlinepersona@programming.dev
      link
      fedilink
      arrow-up
      2
      ·
      3 hours ago

      I feel like people who make these arguments in earnest are simply terrible at change and lack empathy. “Works for me, so I refuse to understand why it doesn’t work for me”. It’s so conservative neckbeard and offputting.

    • Starfighter@discuss.tchncs.de
      link
      fedilink
      arrow-up
      6
      ·
      5 hours ago

      I just wish that they wrote more articles. Their writing style is superb. Can’t argue with this though:

      More coming soon. Or not. I don’t owe you shit.

      • slazer2au@lemmy.world
        link
        fedilink
        English
        arrow-up
        9
        ·
        6 hours ago

        Q: What about team collaboration?

        A: It’s a text file. Put it in Git. You know, that thing you should be using anyway? Now your requests have version control, code review, and diffs. For free. Revolutionary, I know.

      • tourist@lemmy.world
        link
        fedilink
        arrow-up
        2
        arrow-down
        2
        ·
        6 hours ago

        expose a backdoor endpoint on every collaborator’s device and peruse their shell history

    • onlinepersona@programming.dev
      link
      fedilink
      arrow-up
      2
      ·
      3 hours ago

      When you explore an API in a team and would like to collaborate on that with somebody. If you’ve worked on any big tech API, with Oauth, and have secrets, writing a script for every request combination takes way too long. Simply pasting the URL and using the stored oauth token within the session is easy with a frontend. And it’s reusable and sharable within your team.

  • nikolasdimi@lemmy.world
    link
    fedilink
    arrow-up
    10
    arrow-down
    2
    ·
    6 hours ago

    Our team lives in Git, our communication is happening on slack, our docs written and maintained on confluence and after some time they always drift away from the actual requests inside Postman.

    So we built and open sourced Voiden a few months ago: an API tool where all that: specs, tests, context and docs are always together in the same executable plain text file (markdown). We also made this Git native so that every change is versioned and tracked just like code.

    The last change we have made is to add a Runner so that one can run the files directly from the terminal and CI/CD pipelines.

    here is the tool: https://voiden.md/download repo: https://github.com/VoidenHQ/voiden

    welcome to try and give feedback!