Issues with nesting in Abstract objects and mesh properties

Help Speckle v1 (old)
1

I’ve had a few issues dealing with abstract objects that contain nested objects and arrays, and wanted to know what the best practice is to avoid these problems.

The basic idea is:
I have one stream that contains an object that looks something like:

{

    type: "Abstract"
    someParameter : 123,
    nestedStuff: [
        {
            a : 1234,
            b : 1412,
            c : 1125
        },
        {
            a : 4564,
            b : 2323,
            c : 3123
        },
    ]
}

Then in another stream, I wanna make an object that looks like this:

{
    type: "Abstract",
    someParameter : 123,
    nestedStuff: [
        {
            a : 3231,
            b : 2123,
            c : 1114
        },
    ]
}

But of course, when I post that object, it just adds a reference to the first object in the stream… Another scenario would be if I wanted to update the array “nestedStuff”.

I guess I could add my own uuid to each object before creating a new one, but this would be kind of annoying and not sure if it’s the best idea.

2

It’s probably down to not correct hashing of these objects… I’m afraid there’s no silver bullet here :grimacing:

There’s a couple of convenience methods in Core that might give you a leg up in generating these correctly…