Any way to avoid container overwrites in child maps?

[msdrigg]

So I have a nested data type which tracks a number of items like this: {items: { itemId1: {data1: data, data2: data}...}}. Am I understanding the docs right that I should be storing this as {items.itemId1: {data...}} in Loro to avoid potential container-overwriting errors? This does make de-serialization more confusing. And more generally, it means that the nested JSON capabilities of Loro kind of irrelevant because now I have to iterate through all the root keys (including non-item-related keys) and then filter for ones where key.starts_with("items.").

Is there any way to get around this? Maybe there could be some way to specify the child container id manually to avoid collisions/overwrites?

[zxch3n]

Yeah, right now you need to use {itemId1: {data...}}.

Alternatively, you can just use a LoroList, instead of a LoroMap for this. We already have an internal data structure to make looking up ContainerID -> index in a LoroList O(logN), so it's quite efficient.