Opened 9 years ago

Closed 7 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 9 years ago by Tom Trenka

A note: a good majority of this is actually ending up under dojo.config and not under djConfig. Not sure which is better.

comment:2 Changed 9 years ago by Adam Peller

Milestone: 1.4.21.4.3

comment:3 Changed 8 years ago by Adam Peller

Milestone: 1.4.3tbd

comment:4 Changed 7 years ago by Colin Snover

Priority: highblocker

Bulk update of open ticket priorities.

comment:5 Changed 7 years ago by dylan

Milestone: tbd1.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 7 years ago by bill

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:7 Changed 7 years ago by Colin Snover

I agree with bill.

comment:8 Changed 7 years ago by bill

Resolution: fixed
Status: newclosed
Note: See TracTickets for help on using tickets.