Composer boolean expression field no longer supports the expressions type (only equalsExpressions)

[GeoffCoxMSFT]

Describe the bug

Cannot see or edit condition expressions when they don't start with equals (=).

Version

main branch
10/22/2020 9:38AM

Browser

• Electron distribution
• [ X] Chrome
• Safari
• Firefox
• Edge

OS

• macOS
• [ X] Windows
• Ubuntu

To Reproduce

Steps to reproduce the behavior:

1. Create a bot project
2. Add any activity that has a condition
3. Use the drop down to write an expression with the = prefix (=!$Name for example)
4. Close the bot project
5. Edit the dialog file directly to remove the = prefix
6. Open the bot project
7. Select the action and note the state of the condition field

Expected behavior

The expression to continue to appear and be editable for the boolean/expression field because the value is neither true nor false so it must be an expression.

Screenshots

Additional context

[GeoffCoxMSFT]

@chrimc62 - I added you to this issue because the form dialog generator creates conditions without the prefix = which caused this bug to be discovered.