feat(editor): Use text editor

[juliusknorr]

• 🐛 Check issues with sidebar loading when using the new editor
• Add option to switch to the new editor
• Make it default for new installations
  • Ensure .md is the default file format
  • Ensure that the text editor is the default but fallback to easymde if text is unavailable
• Migration process (if notes was installed before)
  • Show information about new editor and suggest to switch to it

From the old pull request

• remember last opened note
• auto title for new notes
• don't break original file, see Markdown files from external editors lose formatting on save text#593 and Markdown files are corrupted text#772
• improve parallel changes from outside of app, see sync causes conflict even if no edits have occurred text#1212
• use correct / other list/task syntax, see Incorrect Task List syntax text#1297
• loading another note with same component (proof-of-concept uses a "hack" which does not allow for a loading indicator)
• "Link file" feature of the Text app could be replaced by a "Link note" feature (?)
• how to provide integrated images to 3rd-party apps using the Notes API?

List of issues this addresses/resolves

• Fixes Integrate Nextcloud Text #331
• Fixes Paste/dragdrop images #918

[newhinton]

how to provide integrated images to 3rd-party apps using the Notes API?

this is already implemented, see here: #785

[newhinton]

Ensure .md is the default file format

We probably should think very careful about that one. Otherwise we have the same issue as in nextcloud/text#593.

Why dont we do the following:

• The user did not change the default file-ending:

  • Use .ncdata if nextcloud/text is used
  • Use .md/.txt if easymde is used (depending on if we want to stick to the current default or change it)

• The user did change the default file-ending:

  • Use what the user supplied

This way we dont get into that whole discussion again, while keeping it relatively simple.

The UX would be that the dropdown for the editor would also change the displayed value for the file-ending. That would not reqire any additional ui-elements.

The additional benefit is that those files would also be editable without the notes app, directly from the files app.

[szaimen]

Is master not protected?

[juliusknorr]

Right, added that.

[julien-nc]

Didn't read the code yet.

1. I face the conflict view after editing in "rich text mode", not waiting for the top-right checkmark to say it was saved, switching to "edit mode" and making a change.
2. After a change in "edit mode", even after the document has been saved (asterisk disappears in the navigation menu), switching to "rich text mode" also brings up the conflict view.

Maybe those issues are not so important as few people will switch between display modes...

Otherwise works like a charm.

[max-nextcloud]

I had a look at the code only. Looks good to me.

[juliusknorr]

Let's handle the conflict when switching separately. We need some extra handling for ensuring that the file is saved before switching views then.