-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
make 'includes' and 'does not include' work as substring tests #44
Comments
We'd like the ability to check whether a string contains another string, so we should ensure that |
I think that's a separate issue. Currently, at least, For example, Maybe it would be fine. Maybe there should be a |
That makes sense. |
I also think what you've said makes sense, Chris. 👍 |
I don't think this will affect lead handling, if flows have rules in place testing 'string' values with these operators. It will cause validation warnings on those flows the next time they're saved.
Remove 'string' operators 'includes' & 'does not include'
After further discussion… 😊 rather than remove these, Wolfe & I decided it would be better to make them operate as substring tests (i.e., as Jones mentioned in the first place), after all. These still won't be full regex operators, though; that would still be a separate operator (say, For the record we also talked about making this string operator have a distinct name other than the array operator ( |
I don't think this will affect lead handling, if flows have rules in place testing 'string' values with these operators. It will cause validation warnings on those flows the next time they're saved.
Looking at this now, I screwed up which issue should be open or closed. The valid string operators are listed here, but the way they work is defined in |
it looks like
includes
anddoes not include
could never behave differently thanis equal to
andis not equal to
. As in this test.Discussion.
The text was updated successfully, but these errors were encountered: