From 72f7edfd0886da1e1c47279d9b0887c566a21305 Mon Sep 17 00:00:00 2001
From: josesimoes <jose.simoes@eclo.solutions>
Date: Thu, 3 Dec 2020 08:08:45 +0000
Subject: [PATCH] Default verbosity is now detailed

- Considering that 99% of use case are developers in CLI, it doesn't make sense to force them to have add this option. When using it in automation scenarious the option to use quiet output can be specified.

***NO_CI***
---
 nanoFirmwareFlasher/Options.cs | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/nanoFirmwareFlasher/Options.cs b/nanoFirmwareFlasher/Options.cs
index 9fbcaf0f..a0ab882c 100644
--- a/nanoFirmwareFlasher/Options.cs
+++ b/nanoFirmwareFlasher/Options.cs
@@ -142,7 +142,7 @@ public class Options
             'v',
             "verbosity",
             Required = false,
-            Default = "n",
+            Default = "d",
             HelpText = "Sets the verbosity level of the command. Allowed values are q[uiet], m[inimal], n[ormal], d[etailed], and diag[nostic]. Not supported in every command; see specific command page to determine if this option is available.")]
         public string Verbosity { get; set; }