This is because at the start of the object's constructor we handle the overrides here:
// Test object specified options
if (options.options)
{
for (p in Options)
{
if (!(p in options.options))
{
options.options[p] = Options[p];
}
}
}
else
{
this.options.options = {};
for (p in Options)
{
this.options.options[p] = Options[p];
}
}
All we need to do is make sure whatever option is specified gets reassigned:
The logic that manages testObject/Library specific overrides seems to be redundant for the storage and decision adapters, I think:
https://github.com/kingo55/mojito-js-delivery/blob/9f313bd1ba59f1f8dcb80cc4df41b6b02b08f28c/lib/mojito.js#L97-L128
This is because at the start of the object's constructor we handle the overrides here:
All we need to do is make sure whatever option is specified gets reassigned:
Unless I'm missing something?