nextcloud / nextcloud/ios

Reformats markdown structure upon saving

Open
#1,619 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Swift
Stars
2.5k
Forks
1k
Avg merge
2d 18h
Merged PRs (30d)
13

Description

Steps to reproduce
  1. Create .md file in Nextcloud with following content:
### Title
#### Subtitle
- 410g flour (100%)
- 267g cold water (65%)
- 8,2g salt (2%)
- 1,6g yeast (0,4%)

#### Subtitle2
- 410g flour (100%)
- 246g cold water
- 8,2g salt (2%)
- 1,6g yeast (0,4%)
  1. Open the document in the iOS app and make some text edits – make sure it saves
  2. View the file (e.g. on desktop) and notice that the markdown was converted (e.g. * instead of -):
### Title

#### Subtitle

* 410g flour (100%) dhshsvs
* 267g cold water (65%)
* 8,2g salt (2%)
* 1,6g yeast (0,4%)

#### Subtitle2

* 410g flour (100%)
* 246g cold water
* 8,2g salt (2%)
* 1,6g yeast (0,4%)
Expected behaviour

Either:

  • (A) the Nextcloud app should not change how I write my Markdown (I haven't had a markdown app so far that automatically reformatted the document. That kind of defeats the purpose of plain text editing tbh)
  • (B) should ask me if doing a conversion is ok and that data can be lost in the conversion

Note: Since the conversion apparently isn't flawless I lost quite some content in my document ... fortunately I noticed that this happens so I only lost part of this one document ...

Actual behaviour

Converts Markdown file (without warning)

Reasoning or why should it be changed/implemented?

The purpose of Nextcloud (in my opinion) is to make sure that data is safe, but changing it without warning and in the process losing data can seriously harm trust in the product.

Environment data

iOS version: iOS 14.6

Nextcloud iOS app version: 3.4.2.0

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No source file, test, or entry point is named. Reproduce the save in the iOS app using the supplied Markdown and compare the resulting file with the original. Done means saving no longer changes or loses Markdown content, or clearly warns before conversion; add regression coverage if the project provides a relevant test location.

Written by the indexing model from the issue text.

Assessment

Tech stack
ios, swift
Domain
content, mobile
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.