Skip to content

ValueControl needs be configurable to avoid utterance conflicts (port ask-sdk-controls/pull/9) #12

@mikelid-zz

Description

@mikelid-zz

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:

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions