DRAFT: Checking for multi/single-value types in UniValue. #27994

Previously it was possible to call getValStr() on a VOBJ and VARR, which silently resulted in the return of an empty string. However, such a call would be most likely a bug. We are now throwing in case of such types.

Similarly, calling empty() and size() didn't make sense for none VOBJ/VARR UniValues.

Please note: This is a draft and not meant to be merged just yet. I created the pull request already because I wanted to see what the CI-Pipeline tells me about this. I also want to give this change another code read pass to convince myself that these changes are actually okay in every case they are currently used.

<!--e57a25ab6845829454e8d69fc972939a-->

The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.

<!--021abf342d371248e50ceaed478a90ca-->

Reviews

See the guideline for information on the review process. A summary of reviews will appear here.

Closing. Although this might be valid, I currently lack the time to check this in detail. If I find the time to properly check it all, I might reopen it.