Opened 11 years ago
Closed 9 years ago
#10516 closed defect (fixed)
djConfig base documentation missing from api.xml
Reported by: | Adam Peller | Owned by: | Neil Roberts |
---|---|---|---|
Priority: | blocker | Milestone: | 1.8 |
Component: | Doc parser | Version: | 1.4.0 |
Keywords: | Cc: | Tom Trenka | |
Blocked By: | Blocking: |
Description
The metadata in bootstrap.js appears to be ok, but all that's showing up are mixins like the one from dojox.analytics/urchin
Change History (8)
comment:1 Changed 11 years ago by
comment:2 Changed 11 years ago by
Milestone: | 1.4.2 → 1.4.3 |
---|
comment:3 Changed 10 years ago by
Milestone: | 1.4.3 → tbd |
---|
comment:5 Changed 9 years ago by
Milestone: | tbd → 1.8 |
---|
This is showing up in dojo/_base/config. I think it can be closed. I guess the real question is, should this show up as dojo/config since most people know it as that?
comment:6 Changed 9 years ago by
Yah I dealt with this in [28890] etc.
It's unfortunate that the config is in dojo/_base/config rather than dojo/config, but I think listing it under dojo/config would confuse people, because when they are trying to *access* the config information they need to do
require([dojo/_base/config], function(config){ ...
rather than
require([dojo/config], function(config){ ...
If you really want it to be under dojo/config then you should probably make an actual top level module called dojo/config that loads dojo/_base/config (or vice-versa). But it's probably not worth it for 1.8, so I would just close this.
comment:8 Changed 9 years ago by
Resolution: | → fixed |
---|---|
Status: | new → closed |
A note: a good majority of this is actually ending up under dojo.config and not under djConfig. Not sure which is better.