When using the Log to Console action, using an expression only outputs that as literal text

Describe the bug

Not sure if this is an issue with the SDK or Composer, so starting here.

If you use the Log to Console action, then set the Text property to an expression, it doesn’t ever evaluate the expression. Additionally, when clicking into the Text field, it prompts/suggests that you can use an expression.

Using string interpolation works fine.

Version

1.2.1

Browser

• Electron distribution
• Chrome
• Safari
• Firefox
• Edge

OS

• macOS
• Windows
• Ubuntu

To Reproduce

Steps to reproduce the behavior:

1. Add a Log Action
2. Set the Text property to be a valid expression such as =turn.activity.from.name
3. Run and test, the value will only be that literal text: =turn.activity.from.name
4. String interpolation such as ${turn.activity.from.name} works as expected/desired.

Expected behavior

Either the expression gets evaluated to the value it should be, or it should not allow/suggest to use an expression. Additionally, information tool-tip should inform this should be only text.

Screenshots

Here is the action:

      "actions": [
        {
          "$kind": "Microsoft.LogAction",
          "$designer": {
            "id": "H0JjmG"
          },
          "label": "trace username",
          "traceActivity": true,
          "text": "=turn.activity.from.name"
        }

  ]

Additional context

[mrivera-ms]

@tdurnford, yes the schema needs to be changed.

LG expressions of the form "Hello ${user.name}" are allowed. Adaptive expressions like "=user.name" are not allowed.

I will submit a PR with the correction to the schema.

[tdurnford]

@mrivera-ms In the SDK Schema, Microsoft.LogActions’s text property is a string expression. Shouldn’t it take a string or an expression that resolves to a string? Is there a difference between an expression and an LG expression - if so, we’d need a way to distinguish between the two in the SDK Schema?