When pulling in Uno.Data.Json
, “String” becomes ambiguous. This almost has to be a bug, because it is at best a huge inconvenience.
As in, you can no longer do String.IsNullOrEmpty without fully qualifying.
Use the keyword when you mean Uno.String
string.IsNullOrEmpty(..)
Thanks for the report, I have raised a ticket to get this issue resolved, the types that causes the ambiguity will be changed, they are not visibile in the public API so it will not break anything