Request: Multiple Collections Support

[UnicodeTreason]

I have many collections, to keep all my API work organised.

If i configure my Zabbix collection to save to file Zabbix.json

I would expect to be able to go into my MessageNet collection and configure that to save to a different file. But currently its tries to save it to Zabbix.json as well.

If I change the form to say MessageNet.json in the MessageNet collection, then the Zabbix collection also starts saving to MessageNet.json

[UnicodeTreason]

Thoughts:

• If I just configured the project once, and the plugin automatically saved each collection to a file of the same name as the collection. That would be nice.
• else
• Being able to configure a seperate file for each collection would be good too, and I imagine possibly easier to implement.

[DCCoder90]

The thought of storing each workspace in a separate file seems easy enough. The plugin could potentially simply store each workspace in a workspaceName-insomnia.json file.

We could modify the providers to accept a workspace name and then modify the pushWorkspace function in index.tsx to pass the "filename" such as:

models.workspace.name+'-insomnia.json'

But for the pullWorkspace method, would have to loop through every file in a repository and see if it ends with '-insomnia.json' and only pull those files (to keep from just pulling down random files).

Taking this route would effectively eliminate the need to configure the workspace file name from the user; However, this could cause issues if people want to store the requests in the same repository as a corresponding project with a standard name.

[lautit]

Hi!

I'm having the same issue, currently working around it by changing the config file name manually, but it triggers a frontend reload every time.

My +1, will try to review the code and find a solution.