Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cross reference internal links to their respective narrows within ZT #352

Closed
3 tasks
sumanthvrao opened this issue Apr 25, 2019 · 1 comment · Fixed by #708
Closed
3 tasks

Cross reference internal links to their respective narrows within ZT #352

sumanthvrao opened this issue Apr 25, 2019 · 1 comment · Fixed by #708
Labels
enhancement New feature or request GSoC Possible GSoC project component

Comments

@sumanthvrao
Copy link
Member

sumanthvrao commented Apr 25, 2019

Internal links in ZT (those which point to conversation in other narrows in the same realm), are clickable in the sense they are opened in the browser through the web-app which redirect then to the narrow. A similar implementation would be to switch to the respective narrow the link is meant for from within ZT itself (Cross reference). A v2 version of this would be to enable copy/paste the current link to conversation in a message later. This when clicked would do the same redirection to the respective target narrow from within ZT. Implementation of this can be split up into phases.

v1 :

  • Identify the current narrow is an internal link.
  • Switch the narrow to the message addressed on clicking the link.

v2 :

  • Enable copy/paste of link to conversation - terminal/OS based solution.
@sumanthvrao
Copy link
Member Author

@zulipbot add "enhancement"

@zulipbot zulipbot added the enhancement New feature or request label Apr 25, 2019
@sumanthvrao sumanthvrao added the GSoC Possible GSoC project component label Mar 18, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request GSoC Possible GSoC project component
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants