Thanks for the work, Justin! I'm wondering if we really should enable both ootb merging providers. If users want to have their own merging picker, they end up with the default providers being registered and disabling them requires a configuration with an empty root.
I wasn't wrong to enable the merging provider in previous versions as this was the only one. With several potential providers, this is different. Therefore I think we should disable both by default - and bump the version to 2.0.0. In addition, the ResourceMergerService is now a little bit questionable - at least some of the methods are. So we should think about it. And finally I want to add optional CRUD support :) Regards Carsten -- Carsten Ziegeler Adobe Research Switzerland [email protected]
