The old config endpoint still works, but will not be supported going forward.

I must say, when using the tool for A/B testing only, the UI is quite counterintuitive and there's too much unnecessary repeating tasks. Some examples: • Setting experiment status in two different places while only one of them has the actual effect • Setting experiment name in two different places • Choosing targeting, tags etc in two different places In those areas, the old setup worked much better but I hope in time the new one will be streamlined as well.

Oh, and is there a way to apply targeting rules similar to "Targeted" feature to an "A/B Experiment" to bucket visitors into the experiment (not a specific variant)? Thanks.

One more. Is it possible to set the "namespace" somewhere from the UI?

Another quick one: can I pass multiple rules into

growthbook.run()

? i.e. sth like this

growthbook.run({
    "defaultValue": 0,
    "rules": [
        {
            "variations": [0, 1, 2],
            "weights": [0.334, 0.333, 0.333],
            "key": "rd005",
            "hashAttribute": "id"
        },
        { "condition": { "id": "123" }, "force": 1 }
    ]
});

That's an interesting use case that we haven't considered though. Basically evaluating an inline feature instead of an experiment.