Noticed that we are using .id in some serialization code. However, in BJS .id isn’t guaranteed to be unique. This could lead to issues when deserializing objects with .id conflicts?
What would be the recommended ways to work around this?
Thanks for the replies! One issue with using .ids is that it gets arbitrarily set in various different functions all over the source code i.e. cloning functions, and usually these are just copies of the name like @aWeirdo mentioned. So it’s usually not something that the user provides all the time, and this could lead to weird behavior