feat:Authorization is passed to collection not to individual request.

[Miguerfi]

an option to add the authorization to collection config.
workflow:
if the Authorization params is not passed to request headers will verify if has in the collection config.

i think if has this feature will be good to users who have a big collection.
you can take some reference from httpie-desktop client.

[grnmeira]

@Miguerfi I think it makes sense for authorization configuration to be at collections level. Currently though someone can get a similar solution for that using environments, have you tried them?

[Julien-cpsn]

@Miguerfi Hello,

Sorry I totally forgot to reply after clearing the notification.
The current app philosophy is that collections are only request folders. I personnally do not like collections containing informations that will affect the requests. On the other hand, I can understading that setting a thing one time is more practical than many times.

I do not know what to do about that. We will discuss it later
I group this suggestion with having a base URL on collections.

Have a great day!

[Miguerfi]

i suggest the feature because i work in a lot of big projects, and this feature will help a lot.
maybe i do a fork to do this in my vacation.

[Julien-cpsn]

@Miguerfi I understand
you can let the issue open so it doesn't get forgotten :)