Renaming a collection after creating it renames the collection but doesn't rename the folder

[raunaq-r]

I have checked the following:

• [X] I use the newest version of bruno.
• [X] I've searched existing issues and found nothing related to my issue.

Describe the bug

Today was my first time using Bruno. When I create a collection, a folder too is created with the same name as the collection. But, when I rename the collection, the folder doesn't get renamed.

I would assume that the folder too got renamed, that way it becomes easier to search it in explorer. A 1-to -1 mapping between collection name and folder name would be ideal.

Tried it in: macOS Sonoma (v14.4.1)

.bru file to reproduce the bug

No response

Screenshots/Live demo link

[Nithishvb]

Hey, I like to work on this one.

[jmgogo]

I prefer that the current implementation does not have these attributes coupled. I name my Bruno folder collection for every project so its purpose is easily identifiable for me. If the project name were automatically renamed, it would make it difficult to differentiate between collections in the Bruno client.

[helloanoop]

I name my Bruno folder collection for every project so its purpose is easily identifiable for me. If the project name were automatically renamed, it would make it difficult to differentiate between collections in the Bruno client.

I am in agreement with @jgome284

I agree that we need to support renaming the collection path on the filesystem. We also need a UX improvement to clearly differentiate between renaming the collection in the bruno.json file and renaming it at the filesystem level. Changing the filesystem-level collection path would require updating the mappings in the Electron store, where we cache details like collection secrets and OAuth sessions.

However, this is not an immediate priority for us, as we have many high-priority tasks to address. That said, we're open to revisiting the priority of this feature if there's broader community interest.