List-based config options that are empty by default are turned into boolean lists in Configured GUI about configured

[MrCrayfish]

Due to type erasure, Configured does it's best to guess which type it is. For an empty list, it relies on the element validator to determine the type. If you simply return true in the element validator, Configured will assume it's the correct value. It just happens to be that Boolean is the first value tested. Basically ensure you have a strong element validator.

[connor135246]

Thanks for responding on Christmas Day!
But as I said in bottom of the first comment, the element validator doesn't exactly work here.
Here are more examples I tried using the element validator:
ConfigValue<List<? extends Integer>> emptyIntConfig1 = builder.defineList("empty int list 1", Arrays.<Integer> asList(), obj -> obj instanceof Integer);
ConfigValue<List<? extends Integer>> emptyIntConfig2 = builder.defineList("empty int list 2", Arrays.asList(), (obj) -> { try { Integer.parseInt(obj.toString()); return true; } catch (NumberFormatException excep) { return false; } });
ConfigValue<List<? extends String>> emptyStrConfig = builder.defineList("empty string list", new ArrayList<String>(), obj -> obj instanceof String);
None of these config options allow me to add values to the lists in the Configured GUI. On the Add... screen, the text I type turns red, and the Done button can't be pressed, no matter what I type.

[MrCrayfish]

Fixed issue in e8c64d0
As for the config value defined in the steps, refer to my previous reply.