Feat: Enhance optional parameter handling in CLI args parser

Added fallback value support for optional parameters when the property type isn't boolean. This ensures proper handling of defaults using property initializers or a defined "default" value. Updated logic improves robustness and clarity in optional parameter handling.

Author: AnnaSasDev

src/CodeOfChaos.CliArgsParser.Generators/ParameterDto.cs

@@ -4,6 +4,7 @@
 using CodeOfChaos.CliArgsParser.Generators.Helpers;
 using JetBrains.Annotations;
 using Microsoft.CodeAnalysis;
+using Microsoft.CodeAnalysis.CSharp.Syntax;
 using System;
 using System.Collections.Immutable;
 using System.Linq;
@@ -49,8 +50,15 @@ private static string GetShortName(IPropertySymbol symbol) {
 
 
     public string GetWithPropertyDictionary() {
-        return IsRequired
-            ? $"parameterDictionary.GetParameterByPossibleNames<{PropertyType}>({Name}, {ShortName})" 
-            : $"parameterDictionary.GetOptionalParameterByPossibleNames<{PropertyType}>({Name}, {ShortName})";
+        if (IsRequired) return $"parameterDictionary.GetParameterByPossibleNames<{PropertyType}>({Name}, {ShortName})";
+
+        if (PropertyType == "bool") return $"parameterDictionary.GetOptionalParameterByPossibleNames<{PropertyType}>({Name}, {ShortName})";
+        
+        string fallback = Symbol.DeclaringSyntaxReferences
+            .Select(r => r.GetSyntax())
+            .OfType<PropertyDeclarationSyntax>()
+            .FirstOrDefault()?.Initializer?.Value.ToString() ?? "default";
+
+        return $"parameterDictionary.GetOptionalParameterByPossibleNames<{PropertyType}>({Name}, {ShortName}) ?? {fallback}";
     }
 }