Opened 15 years ago
Closed 15 years ago
#3020 closed enhancement (wontfix)
Dijit: data binding smarts and properties need to be a mixin
Reported by: | alex | Owned by: | bill |
---|---|---|---|
Priority: | high | Milestone: | 0.9beta |
Component: | Dijit | Version: | 0.9 |
Keywords: | dijit, data, binding, parse | Cc: | alex |
Blocked By: | Blocking: |
Description
Currently tree and the select/autocomplete define properties for locating stores are implemented on an ad-hoc basis. Properties like query, labelAttr, typeAttr, and store should be exposed through a general mixin that knows how to marshall those properties and, at a minimum, locate stores referenced by name.
This is probably just extracting code from Tree.
Change History (3)
comment:1 Changed 15 years ago by
Component: | Widgets → Dijit |
---|
comment:2 Changed 15 years ago by
Status: | new → assigned |
---|
comment:3 Changed 15 years ago by
Resolution: | → wontfix |
---|---|
Status: | assigned → closed |
As it turns out, "labelAttr" and "typeAttr" have been removed, "query" is only for Tree, and mapping a store name to the store itself is done by the parser. So if there was a base class it would just be one line:
store: null
Marking as "won't fix" for now; if things change later we can make a mixin.
See also #3025