When defining synonyms for an input foo, accessing $input.foo should show different values for foo's key and value.
Yet, when using the debugger both key and value are the same.
Current Behavior
For example, I have this intent for the user to ask for an exchange rate. You'll see I've defined a custom type for the currency, and defined synonyms for EUR and GBP.
Notice that for both inputs, the id, the value and the key are all the same —i.e. the synonym used by the user. None is the resolved key value. And the id, well. Not sure what that should be, but I don't think it should be the synonym either.
I'm submitting a...
Expected Behavior
When defining synonyms for an input
foo
, accessing$input.foo
should show different values for foo'skey
andvalue
. Yet, when using the debugger bothkey
andvalue
are the same.Current Behavior
For example, I have this intent for the user to ask for an exchange rate. You'll see I've defined a custom type for the currency, and defined synonyms for EUR and GBP.
When in the intent handler I print
this.$inputs
, this is what I get.Notice that for both inputs, the
id
, thevalue
and thekey
are all the same —i.e. the synonym used by the user. None is the resolved key value. And theid
, well. Not sure what that should be, but I don't think it should be the synonym either.Error log
No error log.
Your Environment