Should md output print verbose and debug option?

[MartinM85]

When implementing a new command with Zod schema, I've realized that md output now contains debug and verbose options

Example:

  # outlook mail searchfolder add --debug "false" --verbose "false" --userName "[email protected]" --folderName "Microsoft Entra" --messageFilter "contains(subject,'Microsoft Entra ID')" --sourceFoldersIds "AQMkAGRlM2Y5YTkzLWI2NzAtNDczOS05YHqjbDnRgQAAAgEMAAAA"

  Date: 9/6/2024

  ## Microsoft Entra (AQMkAGRlM2Y5YTkzLWI2NzAtNDczOS05YHqjbDnRgQABco88oAAAAA==)

  Property | Value
  ---------|-------
  id | AQMkAGRlM2Y5YTkzLWI2NzAtNDczOS05YHqjbDnRgQABco88oAAAAA==
  displayName | Microsoft Entra
  parentFolderId | AQMkAGRlM2Y5YTkzLWI2NzAtNDczOS05YHqjbDnRgQAAAgEEAAAA
  childFolderCount | 0
  unreadItemCount | 27
  totalItemCount | 41
  isHidden | false
  isSupported | true
  includeNestedFolders | false
  filterQuery | contains(subject,'Microsoft Entra ID')

The md output prints the command itself with all options and now the command contains debug and verbose option. I can't say whether it is intended or a bug.

[Adam-it]

I do not believe it is a bug as it is not producing any problem, right?
But at the same time I think this change was not intended and it is something we did not noticed when adding ZOD.

Since it was not planned we may add an issue to fix it up 👍

[milanholemans]

I believe this is because using Minimist, a boolean could have 3 values: true, false or undefined. With ZOD, you can set default values for options. This way you can enforce that a boolean can only be true or false which makes more sense in most cases.

[waldekmastykarz]

This change was not intentional. I suggest we create an issue and clean it up from the output. Thanks for bringing it up @MartinM85