FIX verbose flag

naming conflicted apparently with tuist. when using a different naming e. g. `--verbose-output` it works as expected Resolves #5
mflknr · Feb 19, 2024 · 9e4d560 · 9e4d560
1 parent 564a0f7
commit 9e4d560
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/Sources/TuistPluginOutdated/Commands/SubCommands/Outdated.swift b/Sources/TuistPluginOutdated/Commands/SubCommands/Outdated.swift
@@ -21,7 +21,7 @@ struct Outdated: ParsableCommand {
     var path: String?
 
     @Flag(name: .long)
-    var verbose: Bool = false
+    var verboseOutput: Bool = false
 
     @Flag(
         name: .shortAndLong,
@@ -30,7 +30,7 @@ struct Outdated: ParsableCommand {
     var all: Bool = false
 
     mutating func run() throws {
-        ExecutableState.shared.isVerbose = verbose
+        ExecutableState.shared.isVerbose = verboseOutput
         ExecutableState.shared.addAllDependenciesToOutput = all
         verboseCallback { print("Verbose output enabled.") }