Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Matched parameters' values are always strings #30

Open
5 tasks
mgv99 opened this issue Oct 5, 2023 · 0 comments
Open
5 tasks

Matched parameters' values are always strings #30

mgv99 opened this issue Oct 5, 2023 · 0 comments
Labels
enhancement New feature or request

Comments

@mgv99
Copy link
Collaborator

mgv99 commented Oct 5, 2023

When getting the value of a matched parameter in a state body, e.g.
temperature = predicted_intent.get_parameter('temperature').value
we always obtain a str object, therefore, we cannot do if temperature > 0, since it is a string object. We can simply cast the object to its proper type, but it adds complexity to the body of the state.
We could implement a flexible type value, at least for the following basic types:

  • str
  • int
  • float
  • datetime
  • bool (can a user actually write a bool value in a message?)
@mgv99 mgv99 added the enhancement New feature or request label Oct 5, 2023
@mgv99 mgv99 added this to the Version 1.0 milestone Oct 13, 2023
@jcabot jcabot removed this from the Version 1.0 milestone Nov 15, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants