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

GrowthBook Users

Hi Jorge, that does sound like a bug we should fix.

Ah, I think I know why. We cast attribute values to a string first and it's being cast to "None" instead of an empty string.

<@U01TCPDB58C>
it seems so, and I believe that it is <https://github.com/growthbook/growthbook-python/blob/d18bd7eec05a80944bfedde61eec3786080f3a9c/growthbook.py#L537|this code line> the one that takes the `None` value and makes it `'None'`

It seems like a bug isn't it? So the expected behavior would be casting the `None` to an empty string, isn't it?

This way, the empty string, and the null value will behave the same way

yes, I think if we just change it to this it should work:
```str(self._attributes[attr] or "")```
I can fix this and add an automated test case for it today

Thanks so much <@U01TCPDB58C>, that would be great!!
I'll keep an eye on it to upgrade the sdk version then!

<@U03MS6FJU79> New version is published now with the fix - 0.3.1

BTW <@U01TCPDB58C> do you think the same issue might apply also to the ruby SDK?

Part of our backend is in ruby and that team uses the Ruby SDK

It's possible. I added a new test case to our test suite, so I can add that to Ruby as well to check. I think most languages already treat null as an empty string.