with 2.1 the Value field of a Trace Activity is throwing warnings where it did not previously

Describe the bug

Pre 2.1, I could have the Value field of a trace activity, with a value type of string, without quotes and just call properties as needed. no warning was raised. turn.activity.listOfScores = ${turn.activity.listOfScores} turn.activity.value = ${turn.activity.value} and turn.activity = ${turn.activity}

No single quotes were necessary as they were always implied. I now have hundreds of warnings for trace events properties where there wasnt a problem before.

Version

Version 2.1

Browser

OS

• Windows

To Reproduce

Steps to reproduce the behavior:

Create a Trace Event with a value type of string and enter a string with escaped properties. see screen shots for examples. warning is received.

Expected behavior

the value fields with value type of string should not need quotes since its defined as a value type of string.

Screenshots

Screenshot 1

Screenshot 2

Additional context

[stevkan]

@tonyanziano, I was able to repro the issue once. But, unable to repro any, again. I don’t remember what steps I took to get the error to show in the UI, but everything I tried, including trying to retrace my steps (no pun intended), failed to repro after the first occurrence.

However, a warning is shown in the ‘Problems’ output that does capture the same message that was displayed in the error (see below).

It also doesn’t appear to be a blocking issue. While the warning / error is displayed, it isn’t keeping the bot from outputting the trace. @Uggi, is this your experience, as well?

[srinaath]

@boydc2014 Is there someone on your team to investigate this ticket?