Programatically move a note

[jobidon]

I am trying to move a note in the tree
I found the toggleNoteInParent function which allow me to attach a note to the new path, that's fine, but I am trying to move the note, so I need to remove the note from its current branch as well.
I am assuming that the getParentNotes, getAncestors, getParentBranches functions would consider the clones/copies of the note in the tree, so what I really need is the parent of originEntity.getNote(). How do I obtain that?
Or is there an easier way to move a note in the tree?

[zadam]

Hi, what about this (roughly)?

const note = ... // note I want to move
const originalParentNoteId = note.getParentNotes()[0].parentNoteId;

api.toggleInParent(true, note.noteId, newParentNoteId); // clone to new location
api.toggleInParent(false, note.noteId, originalParentNoteId); // remove the old location

[nicollasricas]

I'm also trying to move a note programmatically but couldn't find any way.

module.exports = async function (noteId) {
  const note = await api.getNote(noteId);

  if (!note) {
    return;
  }

  if (note.getParentNotes().some((m) => m.hasLabel("todoArchive"))) {
    return;
  }

  const todoDoneId = (
    await note.getParentNotes()[0].getParentNotes()[0].getChildNotes()
  ).find((m) => m.hasLabel("todoDone"))?.noteId;

  if (!todoDoneId) {
    return;
  }

  note.removeLabel("timeLeft");

  await api.toggleNoteInParent(false, note.noteId, todoDoneId);
};

If I set the first argument to true, it works but clones the note instead of moving it.

Here's what I'm trying to do: move this "feature note" to the "done" section.

[nicollasricas]

Thanks for the help @sigaloid, but I'm trying to move a note and not cloning it.

I will take the longer path and create a new note inside the parent that I wish to move, copy everything and delete the original. I was just looking for a easier way!

[sigaloid]

I believe that is what zadam describes in the solution to this discussion (correct me if I'm wrong): #2507 (comment)

[nicollasricas]

F me, I found out why it was always cloning the note. I had a previous attribute configured for testing the new update @zadam made. It was cloning after moving it. I didn't see that and was thinking that the "roughly move" wasn't working.

Thanks for all the help!

[nicollasricas]

@sigaloid. Here's why I was thinking the note were cloned and not moved.

Backend logs:

18:05:48.631 [Script TyCL5FFAfV6H] Ensured note bcfcRjT7m5M4 is in parent note iknHvZF0hlRh with prefix undefined
18:05:48.632 [Script TyCL5FFAfV6H] Marking branches 51Kin9H82Ybe as deleted
18:05:48.633 [Script TyCL5FFAfV6H] Ensured note bcfcRjT7m5M4 is NOT in parent note cLYeDipjZqYh

After reloading the frontend:

I hope this helps someone in the future with the same issue.

@zadam Do you see any downside of calling refreshTree or reloadNote after moving the note?

[zadam]

refreshTree() is a no-op (tree self updates, kept in API for BC), reloadNote() shouldn't have negative effects, but also shouldn't be needed.