Method execute

src/commands/CmdAdd.cpp:52–93

///////////////////////////////////////////////////////////////////////////

////////////////////////////////////////////////////////////////////////////////
int CmdAdd::execute(std::string& output) {
  // Apply the command line modifications to the new task.
  Task task;

  // the task is empty, but DOM references can refer to earlier parts of the
  // command line, e.g., `task add due:20110101 wait:due`.
  task.modify(Task::modReplace, true);

  // Validate a task for addition. This is stricter than `task.validate`, as any
  // inconsistency is probably user error.
  task.validate_add();

  Context::getContext().tdb2.add(task);

  // Do not display ID 0, users cannot query by that
  auto status = task.getStatus();

  // We may have a situation where both new-id and new-uuid config
  // variables are set. In that case, we'll show the new-uuid, as
  // it's enduring and never changes, and it's unlikely the caller
  // asked for this if they just wanted a human-friendly number.

  if (Context::getContext().verbose("new-uuid") && status == Task::recurring)
    output += format("Created task {1} (recurrence template).\n", task.get("uuid"));

  else if (Context::getContext().verbose("new-uuid") ||
           (Context::getContext().verbose("new-id") &&
            (status == Task::completed || status == Task::deleted)))
    output += format("Created task {1}.\n", task.get("uuid"));

  else if (Context::getContext().verbose("new-id") &&
           (status == Task::pending || status == Task::waiting))
    output += format("Created task {1}.\n", task.id);

  else if (Context::getContext().verbose("new-id") && status == Task::recurring)
    output += format("Created task {1} (recurrence template).\n", task.id);

  if (Context::getContext().verbose("project"))
    Context::getContext().footnote(onProjectChange(task));

  return 0;
}

////////////////////////////////////////////////////////////////////////////////