Matthew Elwell

PHP PR: https://github.com/Flagsmith/flagsmith-php-client/pull/48

Node.js PR: https://github.com/Flagsmith/flagsmith-nodejs-client/pull/119

I've just realised that using the DjangoId attribute is not a valid solution to this issue since the identity information from the Core API is, in fact, never passed to...

The only solution I can see here is to ensure that all points at which percentage split evaluations are carried out, we use the composite key since this is the...

To confirm, we only need to make this change in the Core API. All the clients are now consistent that they use the Django ID if it exists, otherwise, they...

Latest update: percentage split is still prioritising the `django_id` in our Core API, even if using consistent hashing is enabled. Since v2.85.0 we are [using the flagsmith engine for evaluating...

Some thoughts based on a conversation with @gagantrivedi . 1. Initial idea was to have 'tag based permission' be opt-in and, if enabled, the Update Feature State permission at the...

As discussed on a call with @gagantrivedi , @novakzaballa and @kyle-ssg we have decided on a few outcomes: 1. Roles with a tag should only be able to include permissions...

@kyle-ssg I think you added a PR for this, can you link here?

Hi @SD-13 , I don't know if @oohsai is working on it already? If so, please assign to yourself. If not, @SD-13 feel free to take it.