Order of data setting must be enforced when data set through setConfig

[ExtAnimal]

Forum post

The ordering os data setting means that events is added before resources, so when loading the new events, it looks up the old resources in the resourceStore.

Data loading order is highly defined. It's why CrudManager exists. The order is defined in ProjectConsumer, and it probably is possible to have ProjectConsumer implement the data names (['resources', 'events', 'assignments']), as configurable configs, so that each references its previous (so changeEvents calls this.getConfig('resources') to bring the resources in which it relies on)

That would then mean that the WrapperHelper, instead of passing property changes directly in, would gather up all the configs into a newConfigObject, and on a 0 ms timer, call configOrInstance.setConfig(newConfigObject)

But the immediate concern is what change caused this to begin behaving like this. Something must have changed in the wrapper layer. @jsakalos ?