BUG: inconsistent item serialization when null tag is present

jhardin_accumulajhardin_accumula Member Posts: 4

Folks:

It's possible for the user to define null tags on an item. In the UI it looks like this:

When retrieved via the API, it comes across as this:

"Tags":{"@attributes":{"count":"2"},"tag":["ss18",{}]}

While this may deserialize successfully in Javascript and other weakly-typed languages, it fails basic deserialization in a strongly-typed language that is expecting an array of strings.

I'd like to report this as a bug. It should serialize as:

"Tags":{"@attributes":{"count":"2"},"tag":["ss18",null]}

An explicit null is preferred, but this would also be acceptable:

"Tags":{"@attributes":{"count":"2"},"tag":["ss18",""]}


Thank you.

1 comment

  • Ali_MasoumieAli_Masoumie Moderator, Lightspeed Staff Posts: 383 moderator

    Thank you for reporting this.

    We will do some further testing and will then create a report.

Sign In or Register to comment.