Beta version 1.6.0
Just to show one design goal, which is to recover from common User errors with editing JSON files, here I use Notepad++ to cut and paste the "A" parameter from the top to the bottom of the list. My common error is to not adjust the commas (one is missing, and an extra one is "trailing" the list):
"Pretty Print" will correct such comma errors, so on reading the config we get:
--> Adds support for Sets and Maps in 2019+
Note: with no Sets/Maps in 2017, I am using slower old-school flattening techniques to support them. I can also not add them to my Unit Test suite (as it is in 2017), so this could do with User testing to find edge cases.
I am stuck in LV2018 for hardware that went out of support after that. Really appreciate you making this non-breaking in 2018!
Does it support variant-attribute maps in 2018? I made my own dictionary and set utilities based on them, and would really love to serialize them with your library. I am switching to JSONtext for all forward development.
Does it support variant-attribute maps in 2018? I made my own dictionary and set utilities based on them, and would really love to serialize them with your library.
Going from a Variant-attribute map to JSON is implemented, but the reverse journey is not. The reverse is problematic, as JSON doesn't carry the precise LabVIEW type to convert to, so if I wrote it, it couldn't properly convert any types but strings, numbers and booleans. Which is probably useless for you.
I don't actually use Variant-Attribute Maps like this, but I might be able to help. Possibly I could save type information. Or you could provide a type (if all your Map attributes have teh same type).
Beta 1.6.3 (fix issue with not working for Clusters in Sets/Maps; https://bitbucket.org/drjdpowell/jsontext/issues/74/add-support-for-maps-set