VoidenHQ/voiden

Support the HTTP QUERY Method Use Case Voiden currently doesn't support the HTTP QUERY method, which means users cannot test API endpoints that use it. Proposed Solution Add support for the QUERY method in the Voiden REST API plugin so users can send QUERY requests and test these endpoints just like other supported HTTP methods.

Use Case I'm porting a good number of projects from Postman to Voiden. In this particular case (for reasons unrelated to Voiden) I do so manually. When adding 3 or 4 environments for each, this gets bothersome: create environment, create 7-8 variables and set the values. It would be much nicer if I could create the first environment, fill it with all the required properties and values, and duplicate it, set a new name and just change/tweak the values as needed. I also noticed it's not possible to delete existing environments using the environment editor. Proposed Solution Right-click menu for environment with options: "duplicate" and "delete".

Description Minor annoyance: all windows (for separate projects) opened during any time are re-opened when Voiden is next started (on MacOS). Steps to Reproduce Remove all window-state-* files from /Users/<you>/Application Support/Voiden/window-states/ Start Voiden, open project folder Open new window, open another project folder Close either window Quit Voiden Start Voiden, see both windows open Expected Behavior I would expect either Voiden opens only the windows that were open on the most recent Quit; or open no windows at all. Actual Behavior All windows opened at any time are opened on Voiden launch. Environment OS: macOS 26.6.2 Voiden version: 2.3.1 Additional Context I've had Voiden installed for quite a few versions already. If it makes sense to do a complete reinstall / clean sweep to avoid issues, I can do that.

Use Case Postman/Bruno allows opening multiple collections/workspaces at once. This allows easier testing of various services as the consumer of the APIs. For example, say I need to build a project that interacts with GitHub and Box, I'll want to be able to test both API endpoints easily. The current approach does not allow this as it's more geared towards each service (GitHub as an example) having it's own workspace opened. This means I'll have to create a separate workspace on Voiden if I also need to test Box. Proposed Solution As Voiden has built in support for .env files, allow requests to read from .env from it's entire hierarchy. Or extend Environments capability to be added to a folder instead of the overall workspace. For example: In the following scenario, requests in folder A would build a environment variable using the values from Folder A's .env file. Requests in Folder B would read the .env file from Folder A first, then overwrite any same variables in Folder A's .env fil

Use Case I have several tests checking that certain paths fail under certain conditions and assertions to validate that much. I would like when I run stitch runner to see that those tests passed as all of their assertions have passed, even though the endpoint returned a 4xx/5xx response, because that's a passing test for me.