i've noticed if not use @observable
in of web ui code fields/members changes picked automatically data binding syntax.
the issue run when picking 1 field in class extends webcomponent , applying @observable
annotation, other fields dont bind correctly , display changes.
is known issue or correctly functionality?
if use @observable
annotation once, should applying fields?
as mentioned in post, have option of marking class @observable
.
you're caught between observables , watchers. watchers (and dispatch) old way, phased out. observables new way. in order not break old clients, kept watchers in. if used @ least 1 @observable
, watcher system disabled.
the new mdv v2 implementation getting ready. suggest use @observable
want observed. stop using dispatch()
everywhere. also, stop using observable top-level fields, because won't bindable node.
apologies, things in state of flux. suspect things settle quite soon.
i suggest reading more mdv v2 here: https://github.com/toolkitchen/mdv/blob/stable/readme.md ready change.
i suspect @observable
continue option, it's ok keep using now.
Comments
Post a Comment