mirror of
https://github.com/hoppscotch/hoppscotch.git
synced 2026-04-26 01:06:00 +03:00
[GH-ISSUE #4322] [feature]: Multi-account switcher #1572
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#1572
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 @GetPsyched on GitHub (Sep 2, 2024).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/4322
Is there an existing issue for this?
Summary
Be able to switch accounts without logging out
Why should this be worked on?
Having to log out any time I have to switch accounts and then log back in is frustrating. But it is manageable, probably worth keeping this is low priority unless others request it.
@liyasthomas commented on GitHub (Sep 3, 2024):
Good request 👍
@SuperALKALINEdroiD commented on GitHub (Sep 10, 2024):
is it possible that I can start doing something on it?
@Olly4k commented on GitHub (Oct 9, 2024):
Hi, I'm currently looking for issues as part of a university course. Is this issue still available? I'd like to have a go.
@Olly4k commented on GitHub (Oct 20, 2024):
I've had a look through the current account system in hoppscotch and have come up with the following temporary solution. There should be a button added just above the logout of profile button in the UI. This will display the login modal used when logging into an account. Then when a login option is selected the current user is logged out and the standard login system occurs. Of course this isn't a true account switching mechanism but since any accounts previously logged into will remain linked to hoppscotch, this will decrease the need to logout explicitly and then back in. It will streamline the process a bit for you. I'll put a PR with the proposed changes up soon.
@SuperALKALINEdroiD commented on GitHub (Oct 20, 2024):
I was thinking almost the same, Can I work with you on this?
-------- Original Message --------
On 10/20/24 11:55, Oliver Ross wrote:
@SanskritiHarmukh commented on GitHub (Oct 21, 2024):
Hey @Olly4k and @SuperALKALINEdroiD , Thank you for showing interest in contributing! For now, this issue involves some backend work, so our internal team will be handling it later. However, feel free to explore other open issues in the repo. We'd love to see your contributions.
@GetPsyched commented on GitHub (Oct 21, 2024):
Would it not be possible to delve into back-end code as well? If they're interested in being more involved, I think it's better to allow code contributions without blocking on core maintainers -- they can chime in once a draft PR is made to give some direction.
What do you think?
@liyasthomas commented on GitHub (Oct 21, 2024):
The current evolution of Hoppscotch is to be a platform-agnostic architecture. But as of now, it has several versions: the community edition, the enterprise edition that is self-hosted, the cloud edition, even their desktop app counterparts.
While remembering and suggesting previous user sessions might sound like a trivial feature, completely implemented state management across our platforms can be, in itself, one of the more significant challenges.
@liyasthomas commented on GitHub (Oct 21, 2024):
@Olly4k while our internal team is planning to address this in the near future, if you'd like to explore the feature and spin up something related, we'd be happy to offer guidance and support along the way. Just keep in mind that the solution needs to be compatible with our cloud, self-hosted, and desktop platforms to ensure consistency.
@Olly4k commented on GitHub (Oct 21, 2024):
@liyasthomas To ensure consistency across platforms would it be enough to limit changes to just the hoppscotch-common directory as it seems to be used by all platforms? Also is there a preferred method of contact we can discuss this further on?
@liyasthomas commented on GitHub (Oct 21, 2024):
@Olly4k Join our Discord: http://hoppscotch.io/discord
@Olly4k commented on GitHub (Oct 21, 2024):
@liyasthomas I've just created a forum post on the discord.