Update current workspace during import
Improvement
When importing non-Yaak files, it should be possible to import the same spec again and have it update the workspace, instead of always creating a new one.
When importing non-Yaak files, it should be possible to import the same spec again and have it update the workspace, instead of always creating a new one.
Sign in to leave a comment.
Literally last feature I depend on - preventing me from buying it.
Totally agreed with OP. While development, the app endpoints change, and openapi file gets updated. Having to import the file every time is tedious, also loses our older requests.
I currently import a new one and rename old one with “(old)” tag but doesn’t feel right.
Implementation feels rather straightforward, the imported_from field can be stored per workspace, which will hold plain text or hashed version of absolute path of the file.
I agree, this should definitely exist.
Would it possible to open an openapi schema without creating a workspace? (And it would be great if you could register a context menu option in the explorer, so when I right-click on a .json file, it should say something like “open with Yaak”, and then open that file without having to create a new workspace etc.)
basically like swaggerui, but with editing capabilities, for quickly inspecting schemas :D
Context menu is a neat idea or imports in general. Opening an OpenAPI spec without actually importing would be a huge change in how Yaak functions. Is the issue that you just don’t like having to delete the workspace after you’re done?
I’m using Yaak as a quick inspection + testing tool while reverse-engineering European grocery chain Android apps to build very detailed price-history statistics.
My workflow is roughly:
The pain point is that I can’t just right-click->“open with yaak” a new generated schema and open it in a temp workspace, but that I have to generate a new workspace again, import the spec again, and then throw it away again. Some kind of “quick view mode”, where it just creates a temp workspace and instantly throws it away again, or importing a same named spec again updates the existing workspace would be good.
I know that his use case is probably very niche, and if it’s too much effort you can also just say no. (after all I am not yet a paying customer, as this is just a hobby project right now (hopefully not forever though :P))
Really need this, I have a big OpenAPI schema I wanted to import, and I basically can’t use Yaak without moving around the yaml files until this feature works.
Even when you have zero requests, I was surprised that importing create a new workspace. To me, it would have made sense to create them all in the current one since it’s a “fresh” workspace anyway.
Hi, I just vide-coded a small tool to solve the problem before having official feature. The tool will help merge collections into a multi sub-folders collection, also support converting httpie collection to postman format. I hope it could be useful for someone who’s willing to try
https://github.com/vuon9/postmanizer
I am not sure if this should go into another own feedback entry, but it would directly fit here:
I would love to have the option to import something into the current Workspace instead of creating a new one
Import multiple files at ones (select multiple, with option if to create new separate workspaces or into the current one)
sending folders/entries between workspaces, maybe even simple context menu, copy&paste
Would it make sense to apply the imports at the folder level instead of the workspace level (if a folder is currently selected)?
The reason I’m asking is because, in my use case, sometimes I have to work with monorepos and would like to have only one workspace in yaak for the whole repo.
This means I would like to create a folder for each package an import it’s OpenAPI spec there.
Right now I have to create a workspace for each package.
I agree with this suggestion.
Importing into the selected folder is better practice than having a separate workspace each time.
I have so many REST Requests and good number of managed environments and variables in my existing REST tool that it is impossible to get the time needed to migrate them all into Yaak, all at once. I was looking forward to importing my REST requests as I go, so importing into a selected workspace would be a great productivity feature for me.
This tires me. Please, let us import openapi,swagger,postman etc files into existing workspaces instead of creating a new one. I setup my workspaces. connected git account. encryption. Then i import an openapi file and boom. a new workspace created. please. Thank you. Love you all.
Please add this, this makes it very hard to build a more general workspace consisting of all separate imports