Overview

This issue is created because we need to research for a new data structure to store all note relations and notes tree at all

Required functionality

• Ability to select full note hierarchy as NoteTreePresentation object (all notes with same root note)
• Ability to to go to the root note recursively (to check parent note team and its access policy)
• Ability to extract path to the root note as NoteListPresentation object (for note breadcrumbs)

Describe objects

• NotePresentation

interface NotePresentation {
  noteId: Note['id'];

  noteTitle: string;
}

• NoteListPresentation

type NoteListPresentation = NotePresentation[];

• NoteTreePresentation

interface NoteTreePresentation {
  noteId: Note['id'];

  noteTitle: string;

  childNotes: NotePresentation[];
}

Note: noteTitle should be used after its implementation in api, since it is not implemented - we return full note content as noteTitle and make all related transformations on web part

Note: This is refactoring issue, firstly check out current solution of note hierarchy

Final product of the work

Several schemas related to possible data structures, their possible performance for required functionality, possible issues in future (like scalability or memory limits)