Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

CLValueMap {"ONE": 2} deserialised key value contains length of map #249

Closed
meywood opened this issue Mar 4, 2024 · 0 comments · Fixed by #250
Closed

CLValueMap {"ONE": 2} deserialised key value contains length of map #249

meywood opened this issue Mar 4, 2024 · 0 comments · Fixed by #250
Assignees
@meywood

Comments

@meywood
Copy link
Collaborator

meywood commented Mar 4, 2024 •
edited
Loading

A CLMapValue of {"ONE": 2} incorrectly deserialises the key bytes prefixing it the length of the map eg:

The deserialised key CLStringValue "ONE" is populated with 01000000030000004f4e45 when it should be 030000004f4e45
@meywood meywood self-assigned this Mar 4, 2024
@meywood meywood linked a pull request Mar 4, 2024 that will close this issue
Issues/249 - Fixes for byte serialisation of CLValues type when nested in collection types such as maps and lists etc #250
Merged
cnorburn added a commit that referenced this issue Mar 7, 2024
@cnorburn
Merge pull request #250 from /issues/249
907f6af 
Issues/249 - Fixes for byte serialisation of CLValues type when nested in collection types such as maps and lists etc
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@meywood meywood

Labels
None yet
Projects
Work In Progress
Status: Done
Milestone
No milestone
1 participant
@meywood