More migration blues

I think I have identified the root cause of why some of your rules are still not working even after updating to v13.2.0, thanks to @mdtahidulislam’s report in #issues. The problem lies in the migration logic that was implemented: in migrating the autofill rules to the new matching syntax, it converted all the rules that match the pattern ^abc$ to "abc". The problem is, in v12 and below, Lightning Autofill did a case insensitive match by default, whereas in v13 you have to use the proper regex i flag in order to force case insensitive matching.

The result is, if your old rule was /^email$/, it would still match “Email” in versions before v13 because the match was case insensitive. After the v13 update, this rule was converted to "email", which no longer matches “Email” because it’s now case sensitive.

The fix

To fix this, I will do what I should’ve done from the beginning: make "abc" a case insensitive match by default. I modeled this syntax after Google’s search syntax, and in Google even if you do an exact match with "abc", it’s still case insensitive. Note that after the next update, if you need to force a case sensitive match, then you need to use a regex pattern.