This is very likely a problem that should be fixed in both stache and can-view-callbacks. But in a training, someone was progressively loading a component that was already written to the page.
This would throw an error about the scope in scope.computeData() not being defined.
This warning isn't helpful. But I also think we should support it. Ideally, when stache finds a custom element, it can register a listener of sorts for if that element becomes defined:
This is very likely a problem that should be fixed in both
stache
andcan-view-callbacks
. But in a training, someone was progressively loading a component that was already written to the page.This would throw an error about the
scope
inscope.computeData()
not being defined.This warning isn't helpful. But I also think we should support it. Ideally, when stache finds a custom element, it can register a listener of sorts for if that element becomes defined:
This way, if the component becomes defined, it can instantiate itself with stache's scope.