In Progress
Status Update
Comments
oa...@google.com <oa...@google.com>
ap...@google.com <ap...@google.com> #2
Surely this is something that the developer can handle themselves. If they just have a reference to the Marker then add a custom property to the marker and use that as the id, I don't think we need to start adding more info to Marker objects for everyone.
I would need more use cases where this is out of the developers hands before I would consider putting this in the API.
I would need more use cases where this is out of the developers hands before I would consider putting this in the API.
Description
AppFunctions would like to support native Java/Android object types in the schema function signature.
This include types like:
LocalDateTime
Uri
PendingIntent
While it is possible to directly support these types as is done already for b/400422328 , this type of support will make the object types opaque to an Agent LLM as the SDK does not expose a contract/constructor for how this java/android type should be constructed. For cases where we expect the Agent LLM to construct this java/android type, this direct support approach does not work.
PendingIntent
inHowever, the AppFunction SDK already supports
Constructible
types as data classes annotated with@AppFunctionSerializable
. Hence, the goal is to support "internally swappable" types in App Functions sdk.At a very high level this means when we have a function signature that utilizes a
swappable type
likeLocalDateTime
, it's equivalent metadata representation should be an LLM friendly serializable type like: