Timeline for How to avoid double quotes for is equal to when using segment builder
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 29, 2016 at 14:20 | comment | added | Vicent Galiana | I'm not allowing users to select the operator as this is my logic and requirement I'm hard coding it. Using the predicate builder did the trick, thanks. | |
| Nov 29, 2016 at 13:14 | vote | accept | Vicent Galiana | ||
| Nov 29, 2016 at 13:13 | history | edited | Dmytro Shevchenko | CC BY-SA 3.0 |
added 138 characters in body
|
| Nov 29, 2016 at 13:03 | comment | added | Dmytro Shevchenko | @RichardSeal Thanks, I updated the answer to get the operator properly. | |
| Nov 29, 2016 at 13:02 | history | edited | Dmytro Shevchenko | CC BY-SA 3.0 |
added 20 characters in body
|
| Nov 29, 2016 at 13:02 | comment | added | Richard Seal♦ |
I think the problem is that the operator here is set by the rules engine, not hard coded. The GetResultPredicate ultimately works off the selected StringConditionOperator to work out what the operator is.
|
|
| Nov 29, 2016 at 12:58 | history | answered | Dmytro Shevchenko | CC BY-SA 3.0 |