Hi @Maketank!
Re 3), it’s not a bug, but it might a too cautious approach on our end. The main bottleneck is ensuring that you’ll be able to query server side by various keys, and, depending on driver, strange chars can throw things off (e.g., . is disallowed because it links two subfields). We’ll look into it!
Re 2), yes, we do not serialise empty lists/nulls. Re the component, we could look into this more. We’ll have a think, and get back to you on this one. If i understand the use case correctly, later on in the grasshopper definition you’d want to edit that object and set those initially created props, that are null to start with?
Re 1) there’s several approaches:
Create a custom speckle object with a geometry prop, and all the other values you need:
Here’s how it looks like:
https://speckle.xyz/streams/a41c7ea120/objects/6e2d98b8f9239be26b5e3cdddfd60f28
Extend a speckle object:
First convert your geometry to a speckle, and then add extra keys to it:
Here’s how it looks like: Speckle
