mirror of
https://github.com/hoppscotch/hoppscotch.git
synced 2026-04-25 16:55:59 +03:00
[GH-ISSUE #5361] [bug]: Generate Data Schema is not working #2050
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#2050
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 @shaadcode on GitHub (Aug 30, 2025).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5361
Originally assigned to: @nivedin on GitHub.
Is there an existing issue for this?
Platform
Desktop App
Browser
Chrome
Operating System
Windows
Bug Description
What happened?
When I try to use the Generate Data Schema feature in Hoppscotch, nothing happens.
What I expected is
I expected Hoppscotch to automatically generate a data schema based on the response body or request structure, as described in the documentation.
Steps to reproduce
Go to the Hoppscotch app (web or desktop)
Send a request to an endpoint that returns structured data (e.g., JSON)
Click on Generate Data Schema
Observe that no schema is generated and there is no error
Screenshots
Additional context
Interceptor used: Native app
Hoppscotch version: 2025.8.0
Operating System: Windows 10
Logs and Console Output
Deployment Type
Self-hosted (on-prem deployment)
Version
No response
@jamesgeorge007 commented on GitHub (Sep 3, 2025):
Hi, closing this issue since it is addressed in the latest release. Please feel free to let us know if you have any feedback.