I'm submitting a...
[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report
[ ] Performance issue
[x] Feature request
[ ] Documentation issue or request
[ ] Other... Please describe:
See Issue #8
and PR #9
This issue is to port the same functionality to ValueControl.
It should be possible to create a ValueControl that will accept values [yes|no|maybe] without causing utterance conflicts with AMAZON.YesIntent etc.
Given the changes made in #9, the work is to add new props to allow configuration of filteredSlotType and an intentToValue mapper function.
Expected Behavior
Current Behavior
Possible Solution
Steps to Reproduce (for bugs)
Context
Your Environment
- ASK SDK Controls used: x.x.x
- Operating System and version:
Node.js and NPM Info
- Node.js version used for development:
- NPM version used for development:
I'm submitting a...
See Issue #8
and PR #9
This issue is to port the same functionality to ValueControl.
It should be possible to create a ValueControl that will accept values [yes|no|maybe] without causing utterance conflicts with AMAZON.YesIntent etc.
Given the changes made in #9, the work is to add new props to allow configuration of filteredSlotType and an intentToValue mapper function.
Expected Behavior
Current Behavior
Possible Solution
Steps to Reproduce (for bugs)
Context
Your Environment
Node.js and NPM Info