Query Speckle Object component update

[daviddekoning]

Step 0:

• [x] I've read the contribution guidelines!

(Note that @megankarbowski is actively working on resolving this - this issue to solicit feedback and see if there is any interest in merge it into the main repo.)

Expected Behaviour

We expect the Query Speckle Object component to be able to query all of a Speckle Object's properties, not just the custom properties in the properties key.

While the top-level properties can be accessed via the Expand Speckle Object component, the order of these properties is not guaranteed, and the component is huge. Being able to access all the properties / keys of a SpeckleObject will allow us to build more robust workflows (that don't depend on a particular order of outputs).

Actual Behaviour

You can only query keys inside the properties dictionary.

Affected Projects

This is a grasshopper specific issue.

Proposed Solution

We propose to modify the Query Speckle Object component to start looking for keys at the top level of a Speckle object. This means that definitions that use the existing component would have to update their input path to add properties. at the beginning.

for example:

desired key	old path	new path
properties.volume	volume	properties.volume
type	(not possible)	type

Alternatively, we could make this a new component with a slightly different name and hide the other component.