StorageMaps are currently recreated as StorageWeakMaps when loaded from DATEX.
This happens because StorageMap extends StorageWeakMap and the DATEX type system always prioritizes the last created type definition.
The order of the Type.std.StorageMap.setJSInterface and Type.std.StorageWeakMap.setJSInterface calls has to be switched.
StorageMaps are currently recreated as StorageWeakMaps when loaded from DATEX. This happens because
StorageMapextendsStorageWeakMapand the DATEX type system always prioritizes the last created type definition. The order of theType.std.StorageMap.setJSInterfaceandType.std.StorageWeakMap.setJSInterfacecalls has to be switched.