-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Added properties to collections #718
Added properties to collections #718
Conversation
@thehorse2000 Nice! Fully onboard with supporting this. I I'd like to recommend a few changes. {
"presets": {
"defaultUrl": "",
"defaultRequestType": "",
}
} |
Hey, Thanks for the info. I actually didn't know there was a collections settings area 😿 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@thehorse2000 Nice work. I have a couple more comments. Once these addressed, I feel this should be good to merge.
@@ -94,6 +94,28 @@ const registerRendererEventHandlers = (mainWindow, watcher, lastOpenedCollection | |||
} | |||
}); | |||
|
|||
// update collection properties |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@thehorse2000 You don't need a new electron event. There is already one which handles the updates for Bruno Config file.
Can you update the code to use that?
@@ -114,6 +118,9 @@ const CollectionSettings = ({ collection }) => { | |||
<div className={getTabClassname('headers')} role="tab" onClick={() => setTab('headers')}> | |||
Headers | |||
</div> | |||
<div className={getTabClassname('presets')} role="tab" onClick={() => setTab('presets')}> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Lets place this tab after Tests
and before Proxy
@thehorse2000 @helloanoop Probably this Settings tab for collection could be opened by clicking on collection name in sidebar, the same way how it is working in Postman. It could be then also used to switch quickly environment, because now if I want to run whole collection or folder I have to unfold many subfolders find first request in collection open it and then I can switch environment which is not very user friendly. Also this Collection properties in modal and Collection settings in tab could be merged to Collection tab. It doeas not make sense to me to have two places in app for similar things. |
Agreed.
Agreed. Thinking of a new Tab called |
@helloanoop Resolved the required changes. |
Nice work @thehorse2000 ! PR Merged. |
@martinsefcik This is done.
This is also done. See #989
@martinsefcik I didn't understand. Can you explain this? |
Thanks.
@helloanoop If you have for example the following collection structure:
then you have to unfold first 4 folders to get inside folder with request, then open request and the switch environment. So I meant this that it isn't/wasn't very user friendly. |
@helloanoop I tested 1.2.0 and now I realized that you put this open collection settings action on click event at different place and it does not help much in scenario I described in previous comment (#718 (comment)) Also wouldn't be better to rename this setting tab name from |
I loved this new feature. |
Description
This change introduces storing properties for collections.
Currently, two properties are stored in collections:
This is very helpful to avoid repetition of entering the same URL over and over again.
This also opens up more space for future customizations for the collections.
The collection properties are stored in the bruno.json file of the collection
Contribution Checklist:
For previous comments of this PR. See #707
Monosnap.screencast.2023-10-21.20-47-15.mp4