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

URL support in card description #718

Open
lordofscripts opened this issue Nov 6, 2024 · 5 comments
Open

URL support in card description #718

lordofscripts opened this issue Nov 6, 2024 · 5 comments
Labels
enhancement New feature or request priority: low Low priority issue, nice to have implemented at some point but not urgent

Comments

@lordofscripts
Copy link

Is your feature request related to a problem? Please describe.
Not related to a problem.

Describe the solution you'd like
That the user can use hyperlinks in the card's text description in a manner like HTML documents where the URL is only visible when editing the hyperlink, but that in normal render mode only the URL text is rendered with underline decoration..

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

@trobonox trobonox added enhancement New feature or request priority: low Low priority issue, nice to have implemented at some point but not urgent labels Nov 9, 2024
@trobonox
Copy link
Member

trobonox commented Nov 9, 2024

I've tried to add this before but it is currently prevented by a security feature in the app framework Tauri, which doesn't allow opening all links entered in an app for security purposes. I'm not sure if I want to disable this because of said security concerns, but I might consider it once I migrate to a higher version of Tauri which includes a lot of new and updated features.

@trobonox trobonox moved this to Backlog/Suggestions to consider in Kanri roadmap Nov 9, 2024
@lordofscripts
Copy link
Author

Good point but, who would put a malicious URL in their own Kanban? Doesn't look like an issue for personal, single-user Kanbans. Now, if the Kanban board is shared by multiple people it COULD be an issue. Then again, I wouldn't add people I can't trust in my Kanban. In any case, I only use it for myself (Personal projects, Creative writing & Software development pet projects).
Anyway, I am super happy that there is now a build for my platform (as of 0.8). 👍

@badlydrawnrob
Copy link

@lordofscripts @trobonox I also suggested this feature in #619, which I think is a reasonable one, but I don't know what security implications it'll have if you've gotta strip any malicious code out. Perhaps in the interim you could just colour them (perhaps [ and ](link.com) in grey so they're distinct from the rest of the text)? I dunno. I'm using https://tinyurl.com/ to make them less ugly. Kind of surprised this is a security risk if Markdown is supported in other cases.

@trobonox
Copy link
Member

I can imagine one case where this could be misused, but that would require an attacker to already have full access to your filesystem and then you very likely already have other problems than a potentially malicious link being injected into one of your Kanri boards.
I am strongly considering this feature since I definitely see the use for it, but at the moment development is very slow in general so no guarantee or any estimates I can give at the moment.

@trobonox trobonox moved this from Backlog/Suggestions to consider to Todo in Kanri roadmap Nov 27, 2024
@lordofscripts
Copy link
Author

Well, if security is a concern for a board that isn't shared (they are all single-user), then it might be configured as an application option in Settings (Allow hyperlinks).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request priority: low Low priority issue, nice to have implemented at some point but not urgent
Projects
Status: Todo
Development

No branches or pull requests

3 participants