#7103 closed defect (fixed)
dojox.json.ref.resolveToJson services
| Reported by: | guest | Owned by: | Kris Zyp |
|---|---|---|---|
| Priority: | low | Milestone: | 1.2 |
| Component: | DojoX Data | Version: | 1.1.1 |
| Keywords: | json.ref | Cc: | [email protected]… |
| Blocked By: | Blocking: |
Description
Right now, resolveToJson is fairly closely tied to its use-case (JsonRestStore? and its related classes).
The "services" parameter expects a map of services that can be looked up by the path. But then it expects the service that is found to have a _schema attribute to use as an attribute.
Since resolveToJson is not really concerned with service at all, and really just wants the schemas, I propose that we remove "services" and add "schemas" which is the same map-based lookup, but directly yields the schema. You could easily port your existing code with a dojo.map() from services map to schema map, and this seems like it is more true to what resolveToJson needs.
thanks.
Change History (3)
comment:1 Changed 13 years ago by
| Owner: | changed from Jared Jurkiewicz to kriszyp |
|---|
comment:2 Changed 13 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
comment:3 Changed 11 years ago by
| Owner: | changed from kriszyp to Kris Zyp |
|---|
Note: See
TracTickets for help on using
tickets.
(In [14237]) Better separatation of concerns in architecture Refers #6981 and fixes #7103 and #7098