[helloanoop]

Oauth2 flow is missing (which should be released by tomorrow), Otherwise you shouldn't encounter any pain points. The app has been in development over 2 years, and community (early adopters) has been using it for over year. It's fairly stable except the occasional blip.

I built the tool for myself, I wanted my collections to co-exist alongside my backend code and be able to version it via git. So I ended up creating a human readable markup language to represent requests so that we can use git to version it.

I hope you like it :)

[PH95VuimJjqBqy]

I see the claim of saving everything on the filesystem and collaboration via git.

- Is there a way to handle secrets outside of this flow? - Can we set/reference variables between collections? collection A sets a variable, collection B uses it.

also, a small bit of feedback from someone that briefly played with Bruno this morning.

- moving requests in a collection via drag/drop isn't obvious and it's actually a pain if you're trying to replace the top item. - if I duplicate a request I want the new request highlighted and I would personally prefer if the same tab was opened

[helloanoop]

> I see the claim of saving everything on the filesystem and collaboration via git.

yes, ALL IN on git :) based collaboration

> Is there a way to handle secrets outside of this flow?

Check: https://docs.usebruno.com/secrets-management/overview.html Two ways of handling secrets.

> collection A sets a variable, collection B uses it.

In bruno collection is the first class citizen, environments reside inside a collection. There is plan to support global environments for the use case you mentioned.

> moving requests in a collection via drag/drop isn't obvious and it's actually a pain if you're trying to replace the top item.

yes, this ux needs to be improved and there is a bug in drag and drop which should be fixed.

[PH95VuimJjqBqy]

Excellent, thank you for the quick response.

I'm guessing your recommendation for dealing with separate environments (dev/qa/etc) would then be a single collection with folders underneath and environments defined w/i that collection.

In that sense collections for bruno seem to be more akin to "projects" and are not really equivalent to postman collections in that sense.

That's workable, it good to know the environments are collection specific rather than global.

[helloanoop]

Exactly!

[PH95VuimJjqBqy]

Sorry to deluge you, I found another UI bug.

if you rename a collection with existing requests in it, the result will be two collections, 1 with the new name and 1 with the old name. The new name will have all the requests as expected.

The old name will be a "ghost" collection, you can't seem to do anything with it, including rename it again. If you close bruno and re-open, the old named collection will be gone.

[helloanoop]

I see. If you don't mind, can you post an issue here on our github tracker - https://github.com/usebruno/bruno and any screenshots of the issue

> if you rename a collection with existing requests in it

I am assuming you are renaming directly using the filesystem. I think this is the is issue you are talking about - https://github.com/usebruno/bruno/issues/28