array of objects no longer being parsed in v1.6.7.111
After installing v1.6.7.111, an array of JSON objects is no longer being parsed by object. The parser is now giving the entire array string to the object serializer, which is returning an error as an array of objects is not a valid object to parse. Returning to 1.6.7.107 has fixed the issue.
I’m happy to help troubleshoot this more, but today I did not have enough time to see what all changes have been made to the parsing code to support set/maps that could be causing the issue. Please reach out if I can provide more information
Comments (10)
-
repo owner -
repo owner Actually, I do have a unit test for 1 and 2D arrays of LVObjects (using a demo serializer that just uses XML in a JSON string), and that works. Can you give me a VI that demonstrates teh problem?
-
repo owner Also, the parser should always give teh entire JSON text to the serializer, just with an Offset into that text at teh position of the specific element. Can you check if that offset is wrong or something?
-
reporter The offset is reading 0, so it’s not pulling off the square bracket I think. I need a bit, but I can give you a small zip with the code that isn’t working. I may need to do this later this evening
-
reporter Is the parser part of the JSONtext or the Common Utilities? I may have had an issue where I only updated the JSONtext package, not the other. I’m seeing an upgrade the the Common Science package now as well
-
repo owner That shouldn’t matter, the Common Utilities change is for another package
-
reporter can I get your email address? I will send you some files that will produce what I’m seeing. Maybe I’m using the tool incorrectly and just got away with it somehow. I being paranoid, but I don’t think I can share this code on a public forum like this. There’s nothing in it, but like I’m saying, just paranoid.
-
repo owner Send me a private message on LAVA or NI.com, and I can get you my address that way
-
repo owner Also, have you looked at the Demo LVClass Serializer? In “Example Custom LVClass Serialization” example?
-
repo owner - changed status to resolved
Was a result of Issue #98. Before this, passes a subset of teh string with Offset=0, but now pass full string with a non-zero offset. Serializer assumed a subset and ignored the Offset. Easily fixable by throwing in a Substring with the Offset.
- Log in to comment
I suspect a bug introduced by Issue
#97. And my unit tests must be inadequate.