You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Parameters that are passed along with intents can be marked as required, but no expected data type can be specified. Thus, on the provider side, it must always be checked whether the passed parameters satisfy the requirements.
Describe the solution you'd like
The platform should support the declaration of the expected data type for parameters. It should be possible to specify a JSON schema inline in the parameter definition or to reference an existing JSON schema.
I can imagine registering JSON schemas as capabilities that can be referenced in both parameter definitions and message payload validation. The platform should provide default JSON schema capabilities for primitive data types such as string, number, and boolean.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Parameters that are passed along with intents can be marked as required, but no expected data type can be specified. Thus, on the provider side, it must always be checked whether the passed parameters satisfy the requirements.
Describe the solution you'd like
The platform should support the declaration of the expected data type for parameters. It should be possible to specify a JSON schema inline in the parameter definition or to reference an existing JSON schema.
I can imagine registering JSON schemas as capabilities that can be referenced in both parameter definitions and message payload validation. The platform should provide default JSON schema capabilities for primitive data types such as
string
,number
, andboolean
.The text was updated successfully, but these errors were encountered: