Should we make detectMerge and/or __configureMerge public

Open igorT opened this issue 5 years ago • 1 comments

May 13 '20 21:05 igorT

As https://github.com/emberjs/data/pull/7182 showed, there might be a need to configure merging strategies, but it's unclear whether we should expose the current configure merge mechanism, as you might need to configure detecting merge as well. @runspired mentioned calling it handlePotentialConflict or something like that

May 13 '20 21:05 igorT

We ended up finding use-case for the cache knowing when this has occurred and added an operation to the cache RFC (in lieu of a hook) https://github.com/emberjs/rfcs/pull/854. We do not believe we need the hook to be public.

Nov 17 '22 02:11 runspired