mirror of
https://github.com/hoppscotch/hoppscotch.git
synced 2026-04-26 01:06:00 +03:00
[GH-ISSUE #2135] [feature]: Sync collection from URL #719
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#719
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 @etiennea on GitHub (Feb 28, 2022).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/2135
Is there an existing issue for this?
Summary
Today you can import a swagger file from a URL, but as the swagger file changes the collection does not.
Ideally you would put that url, and it would sync say daily or more and maybe manually with a button.
Sync would keep all the secrets and credentials just add the new routes and remove the ones that don't exist any more.
Why should this be worked on?
Because it means your hoppscotch setup requires less manual maintenance, having a tool like hoppscotch that is out of sync renders it useless and is also a risk for our QA teams that they test something that is not in sync thus causing problems with regressions etc...
@AndrewBastin commented on GitHub (Mar 4, 2022):
@etiennea
Gotcha. I am just not really sure how the semantics of this will work cleanly in the context of Hoppscotch.
There are numerous cases that we have to think carefully about, for example, what would happen then to requests that have been modified and saved for example, how are we supposed to deal with them, for example. I do not know if it is exactly a great idea to implement it this way.
I am really curious of how the workflow is betwen you and your teams between the Swagger file, the collections and QA. If you could elaborate how that works we can keep in consideration your use case. If its private you can find me on the Hoppscotch Discord and DM me from there.