Well, that much I knew would work. The main problem is that I'm
dealing with a fairly large viewModel such that if I were to use the
mapping plugin to convert all of the necessary values to observables,
it would cause the browser the display the "Stop Running this Script"
message multiple times. The nature of it is data regarding
configuration of all fields on all of the documents in a set of
completely dynamic forms (this is a key requirement in the project). I
could divide this into multiple calls separated using setTimeout, but
I would prefer to only do something like that as a last resort.
What I was trying to do was create a dynamic reference to the current
field being configured (this is a form editor) without converting the
underlying data to observables.
So, if the underlying data must be an observable, then I think I could
just create a single set of observables which would contain the data
for a single field and repopulate these as the field being configured
changes. Granted this is a complete step more convoluted, it's still
way easier that trying to use pure Javascript to do it.
Can you think of a better solution to this? Also, why is it that even
with a writable dependent observable as a wrapper, subscriptions don't
work in my example? I figured that because the data had clearly
changed that the observable was notified by the write operation that
it would make sense to notify subscribers at that time, but obviously
this isn't a usage that you were expecting.