Markdown inline code input rule using backticks (`) is missing
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 659
- Forks
- 133
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 110
Description
Nextcloud Text does not support the standard Markdown inline code syntax using single backticks.
For example, inline code is not rendered as inline code when opening/editing a Markdown file in Text like in Collectives. This syntax is already supported in Nextcloud Talk, so it would be useful to have consistent Markdown behavior across Nextcloud applications.
- Markdown syntax is not properly rendered in text
- Markdown syntax is removed after closing text
- Markdown syntax is changed after closing text
- Something else: Please describe more in detail
The Markdown inline code syntax using single backticks (code) is currently not recognized/rendered as inline code in Nextcloud Text.
Example markdown file
This is some `inline code` within a sentence.
You can also use inline code for `npm install`, `myVariable` or `someFunction()`.
Expected resulting markdown file after opening in text
This is some inline code within a sentence.
You can also use inline code for npm install, myVariable or someFunction().
Details
- Nextcloud version: 34.0.3
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
Reproduce the example in Nextcloud Text by opening or editing a Markdown file containing single-backtick inline code, then compare the behavior with Nextcloud Talk. Trace the Markdown inline-code input handling in the Text editor. Done means backtick expressions render as inline code and the Markdown remains unchanged after closing and reopening the file.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, markdown
- Domain
- content, frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 62/100