refactor(treewide): Improve code quality by working with a FileTree

The FileTree has been taken from the implementation written by my for the
Trinitrix project. It alleviates the problem, where functions had to do
many things themselves.

1 files changed, 7 insertions, 12 deletions

diff --git a/src/command_line_interface.rs b/src/cli.rs
index 5d24ae5..fe1b194 100644
--- a/src/command_line_interface.rs
+++ b/src/cli.rs
@@ -2,7 +2,7 @@ use clap::{Parser, Subcommand};
 
 /// A project manager for LaTeX
 #[derive(Parser, Debug)]
-#[clap(author, version, about, long_about = None)]
+#[command(author, version, about, long_about = None)]
 pub struct Args {
     #[command(subcommand)]
     pub cli: Command,
@@ -12,13 +12,17 @@ pub struct Args {
 pub enum Command {
     /// Generates a new part
     #[command(subcommand)]
-    New(SubCommand),
+    New(What),
 }
 
 #[derive(Subcommand, Debug)]
-pub enum SubCommand {
+pub enum What {
     /// Adds a section
     Section {
+        /// The name of the chapter to extend, can be empty when the current_dir is inside a
+        /// chapter already.
+        #[arg(long, short)]
+        chapter: Option<String>,
         /// Name of the new Section
         name: String,
     },
@@ -28,13 +32,4 @@ pub enum SubCommand {
         /// Name of the new Chapter
         name: String,
     },
-    //    /// generates a new project
-    //    Project {
-    //        /// Name of the new Project
-    //        name: String,
-    //        /// Name of the first chapter
-    //        first_chapter: String,
-    //        // /// Name of the first section
-    //        // first_section: String,
-    //    },
 }