Can't insert a link into a Readme.md file in the Text editor
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 659
- Forks
- 133
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 110
Description
I created a Readme.md file with the NextCloud text editor and created the link by adding it with the link button.
However the URLs displayed are not right.
In my Readme.md file the link shows up underlined and coloured like a link, and clicking on it invokes a URL edit dialog.
When I open the Readme.md in emacs, it shows me this pure text, which looks wrong.
- Governing Document (Constitution): \[file cloud link\](<https://cloud.ecocounts.community/f/42486>)
If I try to use this Readme.md file as the source for another display, for instance the Welcome widget which puts the content on my NextCloud landing page, then the links are not clickable.
To Reproduce
Create a readme.md with a list of files in your cloud with a file name and a link to the open it like this:
My File 1: https://my-next-cloud.tld/f/52741
Another file: https://my-next-cloud.tld/f/521112
and so on.
Expected behavior
The markdown link shouldn't have chevrons or slashes that render it useless in some displays.
Screenshots
Server details:
Nextcloud version: 32.0.8
PHP Version: 8.1.34
Database: Ver 15.1 Distrib 10.11.14-MariaDB, for debian-linux-gnu (x86_64) using EditLine wrapper
Client details:
OS: Linux
Browser: Chrome, FF
Browser version: all
Device: all
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the issue in the Nextcloud Text editor with a Markdown link, then compare the saved Readme.md output with how the Welcome widget renders it. Verify whether the generated link markup is valid Markdown and whether the corrected link remains clickable in both displays.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, markdown
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100