[RSDK-9281] Add native type return to Flutter SDK DiscoverComponents

[hexbabe]

RSDK-9281

Add native type return to Flutter SDK DiscoverComponents

Tested locally

[jckras]

LGTM. my only q/comment is who will be reading these results? looking at the photo you included for local testing, the results are a bit difficult for a user to interpret (it is hard to tell if the nested discovery objects are related to the top-level component?). however, if this is primarily for internal use, than I can understand priorities might be different

[hexbabe]

LGTM. my only q/comment is who will be reading these results? looking at the photo you included for local testing, the results are a bit difficult for a user to interpret (it is hard to tell if the nested discovery objects are related to the top-level component?). however, if this is primarily for internal use, than I can understand priorities might be different

Really good point. This is a point of discussion with AV and mobile right now. I think this is a good initial step though https://viaminc.slack.com/archives/C07GTSXSVEC/p1731708356210009?thread_ts=1731688631.621549&cid=C07GTSXSVEC

[kevin49999]

LGTM. my only q/comment is who will be reading these results? looking at the photo you included for local testing, the results are a bit difficult for a user to interpret (it is hard to tell if the nested discovery objects are related to the top-level component?). however, if this is primarily for internal use, than I can understand priorities might be different

Really good point. This is a point of discussion with AV and mobile right now. I think this is a good initial step though https://viaminc.slack.com/archives/C07GTSXSVEC/p1731708356210009?thread_ts=1731688631.621549&cid=C07GTSXSVEC

I do still agree with this point, on the frontend right now I'm playing around with getting this to something useable and it's tricky. The json string for the cameras in the results looks like this:

{
  "fields": {
    "cameras": {
      "Kind": {
        "ListValue": {
          "values": [
            {
              "Kind": {
                "StructValue": {
                  "fields": {
                    "rtsp_urls": {
                      "Kind": {
                        "ListValue": {}
                      }
                    },
                    "manufacturer": {
                      "Kind": {
                        "StringValue": "ONVIF_ICAMERA"
                      }
                    },
                    "model": {
                      "Kind": {
                        "StringValue": "F26C_IR_c3"
                      }
                    },
                    "serial_number": {
                      "Kind": {
                        "StringValue": "EF00000005087E34"
                      }
                    }
                  }
                }
              }
            },
            {
              "Kind": {
                "StructValue": {
                  "fields": {
                    "manufacturer": {
                      "Kind": {
                        "StringValue": "Amcrest"
                      }
                    },
                    "model": {
                      "Kind": {
                        "StringValue": "IP5M-T1179EW-AI-V3"
                      }
                    },
                    "serial_number": {
                      "Kind": {
                        "StringValue": "AMC1083EC3C8118218"
                      }
                    },
                    "rtsp_urls": {
                      "Kind": {
                        "ListValue": {
                          "values": [
                            {
                              "Kind": {
                                "StringValue": "rtsp://admin:[email protected]:554/cam/realmonitor?channel=1&subtype=0&unicast=true&proto=Onvif"
                              }
                            },
                            {
                              "Kind": {
                                "StringValue": "rtsp://admin:[email protected]:554/cam/realmonitor?channel=1&subtype=1&unicast=true&proto=Onvif"
                              }
                            }
                          ]
                        }
                      }
                    }
                  }
                }
              }
            },
            {
              "Kind": {
                "StructValue": {
                  "fields": {
                    "serial_number": {
                      "Kind": {
                        "StringValue": "EF0000000509A87D"
                      }
                    },
                    "rtsp_urls": {
                      "Kind": {
                        "ListValue": {}
                      }
                    },
                    "manufacturer": {
                      "Kind": {
                        "StringValue": "A_ONVIF_CAMERA"
                      }
                    },
                    "model": {
                      "Kind": {
                        "StringValue": "YMA42P_IR_N_AF"
                      }
                    }
                  }
                }
              }
            }
          ]
        }
      }
    }
  }
}

After calling toMap() all those extra keys like "Kind", "StringValue", "ListValue" make it tough to decode.

Though talking with the mobile team, there could be some easy step I'm missing

[njooma]

Q: why use native type? is it because the results are even more difficult to read as raw proto?

[kevin49999]

Q: why use native type? is it because the results are even more difficult to read as raw proto?

If there was a proto for the results / a result maybe not? 🤔

[hexbabe]

Q: why use native type? is it because the results are even more difficult to read as raw proto?

If there was a proto for the results / a result maybe not? 🤔

Clarification: you mean if results wasn't a list of generic pb structs?

[kevin49999]

Q: why use native type? is it because the results are even more difficult to read as raw proto?

If there was a proto for the results / a result maybe not? 🤔

Clarification: you mean if results wasn't a list of generic pb structs?

Exactly, sorry if my wording is off I haven't really worked w/ proto buffers / grpc

[kevin49999]

Q: why use native type? is it because the results are even more difficult to read as raw proto?

If there was a proto for the results / a result maybe not? 🤔

Clarification: you mean if results wasn't a list of generic pb structs?

Exactly, sorry if my wording is off I haven't really worked w/ proto buffers / grpc

Though to provide more context, in the current app we're working on, when working with a robotConfig it's a bit easier to work with when converted to a map (and it's a pb struct)

[hexbabe]

The question that is currently blocking this PR is: can we make this even better for mobile?

And it looks like the answer is no unless we change the proto

if results wasn't a list of generic pb structs?

OK with me merging this? @kevin49999 @jckras @njooma

[njooma]

Let's not merge yet unless it's blocking something. There should be a way to fix the nested struct keys

[hexbabe]

Please see new util handler to unwrap nested "Kind" and "fields" wrappers

See the new output here

[hexbabe]

Further conversations were had and we are not going forward with a unwrapper https://viaminc.slack.com/archives/C07GTSXSVEC/p1732050452559639?thread_ts=1731688631.621549&cid=C07GTSXSVEC