For other readers it is trivial to store Ruby types in hashes and convert back and forth to and from JSON.
See example … (in another thread.)
Not a problem, see:
JSON::Ext::Generator::GeneratorMethods::NilClass
nil.to_json.inspect
#=> "null"
jstore = {:val => nil}.to_json
jstore.inspect
#=> "{\"val\":null}"
hash = JSON.parse(jstore,symbolize_names:true)
hash.inspect
#=> {:val=>nil}
When we say “registry” we now mean “storage” because most of extension storage has moved to JSON files, rather than the registry. (Native dialog sizes and positions are likely still in the registry.)
It would be nice to have parity between Attribute Dictionaries and JSON storage.
This means that the JSON library may need to be extended with a few API specific class generator methods. Not difficult because many have conversion methods to array and/or hash which are already JSON compatible.