A lot of misc fixes to reduce the compiler warnings on the Core and Client library.
Most of the warnings come from nullability annotations, with a lot of false positives.
This also updates the nullability of items encoded and decoded from tuples: this is impossible to prevent null values from being written to the database by someone else, so the application logic should ALWAYS check for null explicitly. Before, the API would "lie" by pretending that the item would be a non-nullable string.
A lot of misc fixes to reduce the compiler warnings on the Core and Client library.
Most of the warnings come from nullability annotations, with a lot of false positives.
This also updates the nullability of items encoded and decoded from tuples: this is impossible to prevent null values from being written to the database by someone else, so the application logic should ALWAYS check for null explicitly. Before, the API would "lie" by pretending that the item would be a non-nullable
string.