Content lost after file renaming from .md to .txt

[cybermyber]

Content lost after file renaming from .md to .txt

[max-nextcloud]

I suspect the file id stays the same after the rename but the file is now opened with the plaintext editor rather than the markdown editor. At the same time it tries to recover the y.js state from the previous editing session which is invalid in the plaintext editor context.

Nice catch! We did not account for that yet.

[mejo-]

I was able to reproduce this. Definitely something we should look into. @juliushaertl @max-nextcloud any idea what is happening here? I would have expected the markdown source to be displayed in the editor instead of all content being deleted 🤔

[max-nextcloud]

I see two ways to fix this:

1. Clear the document state and all related database entries when a rename changes the mime type between markdown and something else.
2. add a mimetype or editor type to the key for finding the document state for a given document
3. both