mirror of
https://github.com/hoppscotch/hoppscotch.git
synced 2026-04-26 09:16:03 +03:00
[GH-ISSUE #3938] [bug]: experimental feature "expand navigation" doesn't work #1377
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#1377
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 @ANSI-C on GitHub (Mar 27, 2024).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/3938
Is there an existing issue for this?
Current behavior
when I open an API via link url the sidebar doesn't get automatically expanded to the API call I land on.
Steps to reproduce
Environment
Production
Version
Cloud
@joeljstephen commented on GitHub (Apr 9, 2024):
Hi @ANSI-C. Sharing a request does not provide others with access to your request or collections. Instead, it generates a link that references your request, and this link can be shared with anyone and they can generate a copy of your request. Could you help us understand what use case you were trying to achieve so that we can understand this better?
@ANSI-C commented on GitHub (Apr 9, 2024):
Yes, we would like a mean to share same requests in a teamwork to be able to use/update them with a fixed link, possibly shown in the browser url, maybe pointed by url fragment, if not available otherwise.
@thetronjohnson commented on GitHub (Apr 9, 2024):
@ANSI-C is there a reason why creating a new workspace and inviting your team to the workspace won't work for you? Workspace are generally the goto option for collaboration
@ANSI-C commented on GitHub (Apr 9, 2024):
what if I want to document the call in an internal ticketing or KB system?
@anwarulislam commented on GitHub (Mar 4, 2025):
@thetronjohnson, this would be a valuable feature for the workspace maybe? a unique link for each request that can be easily shared to that team member.