Error message seems incomplete when validating an empty field

[roanlibelo]

Steps to Reproduce:

1. Run the Check a field on a Salesforce Lead step

• Email Address: jo@thisisjust.atomatest.com
• Field to check: Title
• Select Contain as operator
• Expected field value: bla

6. Press enter.

Actual Result:

Expected Result:

[amcpanaligan]

Here we go again to update the util versions!!

[amcpanaligan]

Oh should this be a cli fix? If not, we need to update all steps to translate empty strings as (empty value)

But if we fix on the cli level, all empty strings will be evaluated as (empty value)

[iamEAP]

Probably best to handle in the util function. We only want it to display empty value in the message, but still evaluate it in the compare itself as an empty string

[amcpanaligan]

^ Yes but the way it works now that, it only access the messages from the compare class and interpolate strings from there. The string get's passed to the return this.pass(messages...). The .compare only returns a bool

[iamEAP]

D'oh! That's right. I was initially concerned about blanket replacing empty string values with (empty value), but after thinking about it for awhile, I can't come up with a situation where I wouldn't want to know that an argument value in a string was an empty string.

So let's do that! Moving the issue to the CLI repo.

The CLI code is a little bit of a nest, but I think the relevant bit is here: https://github.com/run-crank/cli/blob/master/src/step-aware-command.ts#L94