mirror of
https://github.com/hoppscotch/hoppscotch.git
synced 2026-04-26 01:06:00 +03:00
[GH-ISSUE #1992] [bug]: body is being changed for multiple collections #643
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#643
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 @MustafaHi on GitHub (Dec 3, 2021).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/1992
Originally assigned to: @AndrewBastin on GitHub.
Is there an existing issue for this?
Current behavior
I expect it to change only for the current collection(request) and not the rest (unselected ones)
Steps to reproduce
create request and save it
save as new collection and switch to the new
changing the new will change the old.
Environment
Release
Version
Cloud
@liyasthomas commented on GitHub (Dec 3, 2021):
I can't reproduce this at my end, can you produce a screen record to understand the issue accurately.
@MustafaHi commented on GitHub (Dec 3, 2021):
@liyasthomas commented on GitHub (Dec 3, 2021):
Thanks for providing the screen record. We were able to reproduce this behavior. Working on a fix now.
@AndrewBastin commented on GitHub (Dec 3, 2021):
@MustafaHi please wait for like 5-10 minutes and then let me know if the issue is resolved.
@MustafaHi commented on GitHub (Dec 3, 2021):
The issue is Not resolved.
A work around is to refresh after every change/save.
@liyasthomas commented on GitHub (Dec 3, 2021):
Seems like the production deployment took a little bit longer than expected. I flushed the cache and redeployed the fix. I can confirm this issue has been solved in production.
Feel free to reopen if the issue still persists. Force reload the application to take effect the latest changes.