In the candidate and party classes, the more expansive version of the constructors are being used and it includes fields that are fairly optional in many cases. For these, if the .net string that is passed in is equal to null, then that gets passed down to the C++ code and it tried to use it. This will throw an exception in the C++ code and not continue.
Expected Behavior
Null string values in the candidate and party constructors should be allowed for things such as the imageUri, logouri, color, etc.
Is there an existing issue for this?
Current Behavior
In the candidate and party classes, the more expansive version of the constructors are being used and it includes fields that are fairly optional in many cases. For these, if the .net string that is passed in is equal to null, then that gets passed down to the C++ code and it tried to use it. This will throw an exception in the C++ code and not continue.
Expected Behavior
Null string values in the candidate and party constructors should be allowed for things such as the imageUri, logouri, color, etc.
Steps To Reproduce
No response
Environment
Anything else?
No response