Editing conditions values

[amaatouq]

• It is a bit annoying that making a mistake in the conditions (i.e., wanting to change value) requires resetting the entire app. Especially when there are many conditions.
• Also, it is not very friendly that once the app is configured in development, once it is pushed to production, the entire conditions have to be refilled with values (specially when many values exist)

we will need to think of the UX/UI of the conditions and come up with something! :)

[npaton]

For sure. I don't think we might get away with deleting. If you have a bad condition, delete it, add back. Conditions are small, not a big deal. Since we need deletion, we will do it in any case, and if we can avoid the extra complexity of editing, that's great, any time we can limit complexity, it's a long-term win. Deleting is already complex in it's own right, since we need to make sure that no treatment is using the condition. We could push that to verify that the associated Treatment is not used in any batch/game and offer to delete both at the same time, though that would be more complex and little benefit, so just one level, but in any case, we need to do these verifications for both condition and treatment deletion. Ideally we wouldn't show the button if it can't be deleted, but that might just be an overhead we just don't need... anyway, yeah, I'd recommend just supporting deleting over supporting deleting + editing.

As for database synchronisations, I don't know... But it probably shouldn't be magical :) So maybe "export configuration" and "import configuration" buttons. But then what happens when the imported dataset conflicts with the existing data, what happens when that data is already linked to game that already ran. The merging might get hairy. Maybe I'm alarmist, mabe it's all fine. And I'm sure there's an easy solution, like ignoring the problem. But in all cases I'd prefer if we built something that was solid and people can rely on, rather than giving them tools that work part of the time. ;) To think about more.

In any case, I would think this is low priority at the moment. These are convenience features. But for sure, it's important the platform not become a pain in the ass because of this kind of stuff! ;)