addVariableBlobentry should properly associate blobentry to the variable

[dehann]

Calling addVariableBlobentry on an existing variable should push the new blobentry node as well as connect/associate with the variable. Currently this is not happening:

• NavAbilitySDK.rs/src/services/BlobEntry.rs

  Line 595 in 69cf0b7

  let request_body = AddVariableBlobEntry::build_query(variables);

• NavAbilitySDK.rs/src/gql/AddVariableBlobEntry.gql

  Line 36 in 69cf0b7

  id: $variable_id

[dehann]

Hi @Affie , can you perhaps see why the GQL query above (using the parent node to variable.id) might not associate a new blobentry to the variable? I can confirm that the query does create the blobentry node.

The same approach works for addAgentBlobentry but instead uses parent...label, not .id since uniqueness is higher via agent label.

[Affie]

The GraphQL looks correct.
I don't completely understand your code, but his line looks suspect: https://github.com/NavAbility/NavAbilitySDK.rs/blob/69cf0b72533819813b8719d6fbcd8519c31a3d7f/src/services/BlobEntry.rs#L580C5-L580C85

Does it build the Variable ID, if so, I would expect the graph label and variable label and not the Blobentry label.
So variable_id: nvafg.getId(&format!("{}{}",variable_lbl)).to_string()?

[dehann]

ah that .rs signature is so ugly, this the internal function should rather be:

nvasdk::_getId(nvafg, varlbl)

These signatures should instead implement a Trait for more dispatch-like behavior. My sense we need a trait DistributedFactorGraphs and then instead implement the function _getId(impl DistributedFactorGraphs, &str)