it's one of the first things that a data scientist friend of mine asked. Featurevisor SDK is stateless, in the sense that it evaluates features against given a

it's one of the first things that a data scientist friend of mine asked. Featurevisor SDK is stateless, in the sense that it evaluates features against given attributes and the content of the currently parsed datafile. if we want to have native support of exclusions in the SDK, it has to become stateful on its own. either in memory, device level, or having a backend service that's aware of the session to go cross-device. therefore, it currently does not support it. but I am open to exploring an API for it in future. as a work around, what can be done for now is to track manually whenever a feature is activated (SDK has onActivation handler), and then pass that knowledge as an attribute when evaluating another feature. The second feature can then have a `not` operator in its segments to exclude itself in that case. Links that can help: Activation: https://featurevisor.com/docs/sdks/#activation https://featurevisor.com/docs/sdks/#activation `not` operator: https://featurevisor.com/docs/segments/#not https://featurevisor.com/docs/segments/#not