https://www.growthbook.io/
Join Slack
Would like to see support for commas in string values, right now if we set a condition to match in a...
# give-feedback
b
Would like to see support for commas in string values, right now if we set a condition to match in a set, and the property string value has a comma, it will split the string into separate tokens (even in advanced mongodb mode)
Specific context for this request is we send deviceModel property as a user trait, and we want to serve different values based on model, however iPhones are defined as iPhoneX,Y e.g. iPhone7,4 and we are unable to match because the comma gets interpretted as separate values in a list
f
There's a workaround for advanced mode right now. Basically have to force the condition to be complex enough so it doesn't try parsing it and just leaves it as-is. If you wrap the condition in an 
$and
operator, that should work. For example:
Copy code
{
  "$and": [
    {
      "deviceModel": {
        "$in": [
          "iPhone7,4",
          "iPhone8,0"
        ]
      }
    }
  ]
}
I'll add an issue to our GitHub to fix this so a workaround isn't required
b
We tried using the advanced mode, but when you hit to save, it converts it back to the simplified token split
Oh, I see missed the part of adding an $and operator
Will try that out
appreciate the prompt response!
f
No problem. I added a GitHub Issue for this bug. Don't know when we'll be able to get to it, but it's on our radar now. Thanks for reporting this! https://github.com/growthbook/growthbook/issues/2027
❤️ 1
78 Views
Open in Slack
PreviousNext
Powered by

GrowthBook Users

Open source platform for stress free deployments, measured impact, and smarter decisions.

Powered by