mirror of
https://github.com/hoppscotch/hoppscotch.git
synced 2026-04-25 16:55:59 +03:00
[GH-ISSUE #5177] [bug]: OpenAPI import - request baseUrl variable missing #1972
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#1972
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 @MSP-Stev on GitHub (Jun 20, 2025).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5177
Originally assigned to: @anwarulislam on GitHub.
Is there an existing issue for this?
Platform
Web App
Browser
Chrome
Operating System
Windows
Bug Description
The OpenAPI import creates all request without baseUrl variable.
Cloud & Self-Hosted, Web App and Desktop app have same result.
Steps to reproduce
Screenshot
Other API clients replace "./" to baseUrl, as far i can tell
Deployment Type
Hoppscotch Cloud
Version
No response
@SujalBhatt commented on GitHub (Jun 26, 2025):
Hi !! I'd love to work on this issue as a first-time contributor. It looks like the import logic isn’t correctly using the
servers.urlfrom the OpenAPI spec — I’ll investigate and submit a fix. Let me know if it’s okay to proceed!@liyasthomas commented on GitHub (Jun 26, 2025):
@SujalBhatt you can give it a try.
@SujalBhatt commented on GitHub (Jun 26, 2025):
Thank you so much @liyasthomas , I will try my best !!
@jamesgeorge007 commented on GitHub (Jul 14, 2025):
Hi @SujalBhatt, thanks for taking on this issue!
This one was prioritised for an upcoming patch release, so @anwarulislam from the team has addressed it in #5232.
Appreciate your willingness to help - please feel free to check out other open issues in the meantime. We’d love to have you involved in future contributions!
@jamesgeorge007 commented on GitHub (Jul 16, 2025):
Closing this issue since it's addressed in the latest release.