Branch with descendants can be merged with preceding or following
Might cause a broken tree if with undo
Merge the preceding note in the current note, instead, if current has descendants, Ticket0729
Default behavior is now to merge preceding into current, Ticket0729
Little issue, cursor will be set in preceding not on undo, instead of being set in the current note
Default behavior for merge with following is to merge current into following, Ticket0729
That means that both are now inverted. You feel like it's the following note which is merge into current, but it is the opposite.
That allows to easily manage descendants and undo action
Added a guard to prevent merging from a descendant, with descendants, to a parent, Ticket0729
Restored normal default behavior for merging with preceding, Ticket0729
New behavior will now kick in only if the current note as descendant
Prevent backspace to delete a empty note if it has descendant
Prevent following note to be deleted if empty but has descendants
Ticket0729: Enable mergeWithPreceding with descendants