mirror of
https://github.com/hoppscotch/hoppscotch.git
synced 2026-04-25 16:55:59 +03:00
[GH-ISSUE #4674] [feature]: Add persistence to realtime message #1736
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#1736
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 @hms5232 on GitHub (Jan 14, 2025).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/4674
Is there an existing issue for this?
Summary
Add persistence to message under realtime tab. Just like the REST tab.
Or even, add collections , environment for realtime will be useful!
Why should this be worked on?
Hoppscotch have persistence on WS address (according to #1196 ) but the message doesn't. It will be better to have this feature.
For example, you need to connect a websocket server, and use a fix format to auth and chat:
If I switch tab (not only REST..., but also Socket.IO, MQTT tabs) those message will be missing! I need to key in them one by one again. The only way to avoid this is two browser tab, one for WebSocket (or and tab under realtime) one for REST or others.
Therefore, I think maybe Hoppscotch can add a persistence to message under realtime (the last input will be fine), or even the collections feature. That will be wonderful.
@BrenoBeierstedt commented on GitHub (Feb 5, 2025):
There's an open request just like this one, #3311. It would be a very welcomed feature +1
@hms5232 commented on GitHub (Feb 5, 2025):
Yes! Collection for realtime is very good. If can't, I will hope the persistence can be implemented.