mirror of
https://github.com/hoppscotch/hoppscotch.git
synced 2026-04-25 16:55:59 +03:00
[GH-ISSUE #4052] [bug]: Code generation not working #1440
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#1440
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 @gduverger on GitHub (May 9, 2024).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/4052
Is there an existing issue for this?
Current behavior
When I click "Show code," a popup appears with an error message saying, "Something went wrong." This happens with every language I select. I was expecting to see code generated in the selected language to replicate the query. Specifically, I want to view the cURL generated code to help debug another issue I'm facing.
Steps to reproduce
Environment
Production
Version
Local
@joeljstephen commented on GitHub (May 10, 2024):
@gduverger Thanks for reporting this issue.
We've identified the cause of this issue and opened a PR (https://github.com/hoppscotch/hoppscotch/pull/4033) to fix this. This will be patched in the next immediate point release.
Possibly a duplicate of https://github.com/hoppscotch/hoppscotch/issues/4008 , https://github.com/hoppscotch/hoppscotch/issues/4036.
@liyasthomas commented on GitHub (May 11, 2024):
Thanks for your patience and valuable feedback. This issue has been resolved in the latest release.
Closing this ticket as the fix is now available in the recent version. Please feel free to reach out if you have any other concerns.
@stephenc-dg commented on GitHub (May 7, 2025):
I'm still getting this same error on version 2025.4.1