mirror of
https://github.com/hoppscotch/hoppscotch.git
synced 2026-04-25 16:55:59 +03:00
[GH-ISSUE #4018] [feature]: Choose default authorization type in a collection #1420
Labels
No labels
CodeDay
a11y
browser limited
bug
bug fix
cli
core
critical
design
desktop
discussion
docker
documentation
duplicate
enterprise
feature
feature
fosshack
future
good first issue
hacktoberfest
help wanted
i18n
invalid
major
minor
need information
need testing
not applicable to hoppscotch
not reproducible
pull-request
question
refactor
resolved
sandbox
self-host
spam
stale
testmu
wip
wont fix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/hoppscotch#1420
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @julien4215 on GitHub (Apr 29, 2024).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/4018
Is there an existing issue for this?
Summary
By default, in a collection all requests have the authorization type set to None. It would be nice if there was an option to set the authorization type to inherit instead.
Why should this be worked on?
This is especially useful when importing a collection from OpenAPI.
@julien4215 commented on GitHub (May 30, 2024):
Why was this issue closed ?
Is it because I didn't explain clearly the issue or because you are not interested in adding this feature ?
In case this was misunderstood, I know that the inherit option already exists but what I am asking in this issue is a way to automatically set all endpoints to the inherit option so that you don't have to do it by hand for each endpoint.
@nivedin commented on GitHub (May 30, 2024):
Now a new request saved will have "inherit" as the default authorization and not "none" which have been implemented in the previous release so closed the issue. Overriding a already saved auth type to inherit is not a good flow. If this does not solve your issue please free to open another issue.
@julien4215 commented on GitHub (Jun 15, 2024):
I see, I explained the issue poorly. I'll make a new one.