Hi Jason,
Yes, I would expect that the original "overwrite" and "overwriteProperties"
directives could simply be deprecated and any existing usages in the wild
could be re-mapped to an equivalent "sync mode" by the runtime with a
warning message logged about the deprecation. The available "sync
That would be a great addition. It may be hard to change the existing options
as that could break downstream use cases but I'm sure there's ways of updating
this. I took a look at the code and I'm not familiar enough with oak in this
use case to make that change.
- Jason
On Thu, Dec 6,
Hi Jason,
I would think the ContentLoader could be enhanced to provide more granular
import logic than the "overwrite" and "overwriteProperties" directives
provide.
For a point of comparison, in a previous (non-sling) project I worked on we
had a similar mechanism for importing content into a
We've set up a process to import content into our Sling instance and
we're running into a problem with the ContentLoader.
The use case is that a set of data that is managed in another part of
our company is being provided to us in the form of a JSON object for
loading into our Sling environment.
