Setting blob metadata with empty string VALUE but valid key STILL throws exception
jwilson-proag opened this issue · comments
My issue is the following is still an issue despite being reported almost 3 years ago, and a PR was requested for a fix over a year ago.
I assume this was completely forgotten about? Could we get this addressed so we no longer have to check for null or empty values before adding metadata? Thank you.