Add "Not" predicate operator in the Segment rules

[dabeeeenster]

We should have an "Add AND NOT" as per below:

Would also mean updating https://github.com/Flagsmith/flagsmith-engine

Update Feb 2022!

Actually think a better solution here is to NOT the segment override within the specific flag. So when overriding a flag, allow the user to NOT the segment. I.e.

I want all users NOT within this segment to receive this override.

[kyle-ssg]

Added frontend under flag "not_operator", presumed format would be type:"NOT". The flag allows for adding an array of supported clientside evaluation SDKs (see staging for an example, leaving empty will remove the tooltip).

[
  {
    "type": "ALL",
    "rules": [
      {
        "type": "ANY",
        "rules": [],
        "conditions": [
          {
            "operator": "EQUAL",
            "property": "test",
            "value": "test"
          }
        ]
      },
      {
        "type": "NOT",
        "conditions": [
          {
            "property": "test",
            "operator": "EQUAL",
            "value": "test2"
          }
        ]
      }
    ],
    "conditions": []
  }
]

[khvn26]

As discussed internaly, the proposed operator should actually be "NONE" (and is already supported by engine implementations).

[kyle-ssg]

This is now available under the not_operator flag, I've tested my end and users do seem to be correctly assigned to segments based on the rules.

[Dogacel]

Hi, is the frontend of and not still being implemented? I am not able to see the and not button in our on-prem setup.

[dabeeeenster]

Heads up @kyle-ssg ?

[kyle-ssg]

This is now available under the not_operator flag, I've tested my end and users do seem to be correctly assigned to segments based on the rules.

This @dabeeeenster, we need to simply turn on the not_operator feature for self hosted defaults if we're happy with it.

[dabeeeenster]

OK! NOT operator is live for self hosted installs.