minor adjustments

Author: weezy20

src/commands/add/mod.rs

@@ -11,7 +11,7 @@ pub(crate) struct AddArgs {
     /// Pallet to add to the runtime
     pub(crate) pallet: AddPallet,
     #[arg(global = true, short, long)]
-    /// Runtime path;
+    /// Runtime path; for example: `sub0/runtime/src/lib.rs`
     /// Cargo Manifest path will be inferred as `../Cargo.toml`
     pub(crate) runtime: Option<String>,
 }
@@ -37,9 +37,8 @@ impl AddArgs {
         let runtime_path = match self.runtime {
             Some(ref s) => {
                 let path = PathBuf::from(s);
-                // println!("Using runtime path: {}", &path.display());
                 if !path.exists() {
-                    anyhow::bail!("Runtime path does not exist: {}", path.display());
+                    anyhow::bail!("Invalid runtime path: {}", path.display());
                 }
                 path
             }

src/engines/pallet_engine/steps.rs

@@ -30,12 +30,6 @@ pub(super) enum Steps {
     /// PalletEngine State transitions
     SwitchTo(State),
 }
-
-macro_rules! steps {
-    ($cmd:expr) => {
-        steps.push($cmd);
-    };
-}
 /// Some rules to follow when constructing steps:
 /// The pallet engine state expects to go as edits would, i.e. top to bottom lexically
 /// So it makes sense for any given file, to first include an import, then items that refer to it
@@ -47,6 +41,7 @@ pub(super) fn step_builder(pallet: AddPallet) -> Result<Vec<Steps>> {
         AddPallet::Template => {
             // steps.push(RuntimePalletDependency(Dependency::runtime_template()));
             steps.push(RuntimePalletImport(quote!(
+                // Imports by pop-cli
                 pub use pallet_parachain_template;
             )));
             steps.push(SwitchTo(State::Config));