mirror of
https://github.com/hoppscotch/hoppscotch.git
synced 2026-04-25 08:45:58 +03:00
[GH-ISSUE #5805] [feature]: Update OpenAPI collections #2271
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#2271
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 @DanielGekeler on GitHub (Jan 26, 2026).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5805
Is there an existing issue for this?
Summary
Enable the user to update OpenAPI collections that were imported from URL when the OpenAPI specification changes.
Why should this be worked on?
As a backend developer, I use hoppscotch to interact with my APIs. I usually import OpenAPI specifications via a URL. When making changes to endpoints, I have to remove the collection and import it again to update hoppscotch.
It would be useful to have a button in the context menu of the collection to update it. This button should fetch the OpenAPI specifications from the original import URL and apply any changes without requiring me to enter the URL again.
@bittoby commented on GitHub (Feb 23, 2026):
@liyasthomas @jamesgeorge007 Can i pick this up?
@saksham242007 commented on GitHub (Mar 13, 2026):
Hi! I’m interested in contributing to this feature.
For a first step, I’m planning to add a helper function that fetches an OpenAPI spec from the original import URL and parses it into a JavaScript object, supporting both JSON and YAML. This will serve as the foundation for updating collections later.
I’d love any feedback on this approach before I start working on it.