Multi-level Indentation getting lost in MD file when user edits task using Modal

[tu2-atmanand]

Currently, the plugin is only able to detect and display Subtasks and Task Description body with only one level of indentation. But say if there are subtasks and also the Task Description has content with indentation more than 2 levels then this is not detected and displayed on the board.

• [x] Issue : Because of the above things what is happening is, while scanning, for the lines with more than 1 levels of indentation, their indent is removed using remove trailing spaces (.trim()). And if say user updates this task using Modal, the task gets overwritten in the MD file, where all the two and more indentation gets removed and all content is brought to first level of indentation.
• Possible solution, dont remove trailing spaces while saving in the json file, or add a /t for each level of indentation in the content, I dont understand, how will I store them.

[tu2-atmanand]

• [ ] The possible solution or the best solution for this problem would be if i able to implement the feature from the issue #37

[tu2-atmanand]

This Issue is getting solved currently. I am using the method to store the indentation along with the task.body lines. So, for this i have solved, the method to display Sub-tasks, with any level of indentation and The Task Description (That is any line without the checkbox patter) will be shown as usual. Because my Task Board is not going to show, indentation more then on level in the Description part. The most important work which is left to blend this new changes i have made to store the indentation for the task.body items is :

• [x] The function taskElementsFormatter will only be used to display the content inside the EditTaskModal, So, for this, the Order should not be chaned, because right now i am keeping all the subtasks first and then all the rest of the lines after subTasks, so this has to be changed.
• [x] Created new function, which will give me the data to be replaced in the MD parent file, whenever any changes happens. So this will solve the main problem of this issue. (If in future, you feel this and above function can be combined, then combine them).
• [x] After this new function is ready to give the format correctly preserving the previous structure and only changing the required, fields, see the functions in the taskItemUtils file, if its able to replace the content correctly by matching proper regEx.
• [x] The function updateTaskInJson is also not working, it removed all the lines, when i edited one of the bodyLines

[tu2-atmanand]

DEV : Keeping track of the original data :

[tu2-atmanand]

This issue has been solved.

• The issue with the live preview inside the AddOrEditTaskModal was due to the Borders theme and when the Style Settings plugin is enabled.
• As of now, after editing, the order of the lines inside the task.body is mainatained, even from this Modal since i was using a strange code here, so i thaught, it might be bringing all the normal body lines on top and rest of all the subTasks at bottom, but thats not the case and the code is working even using the following code, the order is maintained :

  const handleSave = () => {
      const updatedTask = {
          ...task,
          title,
          body: [
              ...bodyContent.split('\n'),
              ...subTasks,
          ],
          due,
          tag,
          time: newTime,
          priority,
          filePath: filePath,
      };
      onSave(updatedTask);
      onClose();
  };

[tu2-atmanand]

This issue has been solved, now, the plugin is able to detect multi-level bodyLines and subTasks and also preserve their indentation levels and the order of the lines, when writing back to the file.

• [ ] Closing this issue, but keeping it in Review column to test this functionalities again, to ensure it works with the further implemented changes after this point.