So in the A B and C example above, I want to share foo with two-way into B and C from A, but instead I package up
foo into bar which is observable, and then push bar into B and C using one-way binding to-child.
so if B flips the value of
bar.foo, C will also see it because it's observing the same object.
the value I’m trying to set with the radio button is only important within its model
and is a very weird name:
sellsAllCatalogListings so chances are tha I’m not using the same one on another level and that causes trouble
one thing I noticed today though is a lot of warning because of the old style bindings and an incorrect use of the type in my variables, could a warning be related to this issue?
warning 1:
WARN: can-define: the definition for ok on DefineMap uses a constructor for "type". Did you mean "Type”?
warning2:
WARN: can-stache-bindings: the data binding format {($value)} is deprecated. Use value:bind instead
You should fix that first one, though.
And also give your DefineMap subclasses names. :)
If you extend a DefineMap without a name, it's still got "DefineMap" as the name
which can make it harder to track down "the definition for ok on DefineMap"
can-component actually generates names for the DefineMap subclass if you pass plain objects (i.e. DefineMap prototypes) in as the viewModel
I'm not saying to do that. I am saying, when you extend a DefineMap, it's good practice to give the extended map a name.
It should suffice to add
xhrFields as a param to the options object, if you can also link to somewhere that explains the format.
Anyone know the new CanJS 3 version of can/map/delegate? https://v2.canjs.com/docs/can.Map.prototype.delegate.html . I'm trying to do essentially the same thing... Give it a Map to watch, and if this particular property changes, do stuff
We were shockingly uncreative about some of these package renames
right, I guess I'm trying to find "whatever is the new way" to watch a Map value change
specifically listening to the value of an item in another map, exactly
For can-define/map/map (this would require some migration work): https://canjs.com/doc/can-define/map/map.html
If you want to do this outside of a map's property, you can use can-compute instead: https://canjs.com/doc/can-compute.html
The general idea is pretty much the same between a getter on a defined map or a getter-setter in can-compute: Any other compute or property of a can-map or DefineMap that is read by the getter will cause the value to update when it changes.
And A.foo is a getter that reads the value of B.bar...
And (this is important) A.foo is bound
Then the getter for A.foo is called every time B.bar is updated.
In practice, that looks like this: