fix: handle empty string/hyperlinq interaction

rdavisau · Apr 27, 2019 · 6a3e930 · 6a3e930
1 parent 758b61a
commit 6a3e930
Showing 1 changed file with 6 additions and 1 deletion.
diff --git a/src/DumpEditable/EditorRule.cs b/src/DumpEditable/EditorRule.cs
@@ -101,9 +101,13 @@ public static EditorRule ForTypeWithStringBasedEditor<T>(ParseFunc<string, T, bo
                     ? NullString
                     : (isEnumerable ? JsonConvert.SerializeObject(currVal) : $"{currVal}");
 
+            // hyperlinq doesn't like empty strings
+            if (desc == String.Empty)
+                desc = EmptyString;
+
             var change = new Hyperlinq(() =>
             {
-                var newVal = Interaction.InputBox("Set value for " + p.Name, p.Name, desc);
+                var newVal = Interaction.InputBox("Set value for " + p.Name, p.Name, desc != EmptyString ? desc : String.Empty);
 
                 var canConvert = parseFunc(newVal, out var output);
                 if (isEnumerable)
@@ -136,5 +140,6 @@ public static EditorRule ForTypeWithStringBasedEditor<T>(ParseFunc<string, T, bo
         public delegate V ParseFunc<T, U, V>(T input, out U output);
 
         private const string NullString = "(null)";
+        private const string EmptyString = "(empty string)";
     }
 }