package name with "/" no longer works

[brianlschultz]

The following package name "fd/mobile" does not work anymore for the dojoConfig or during the dojo build process. Maybe there is a different way to handle these now. It worked for us in dojo 1.7.3 but not in 1.8.6

We where able to fix in dojoConfig by using a map and using "fd_mobile" as name in package.

map: {

"*": {

"fd/mobile": "fd_mobile"

}

}

In dojoConfig: packages:[{name:'fd/mobile', location:'../../${AK_JS_PATH}/javascript/fd/mobile'}]

In build profile:

packages:[

{

name: "dojo", location: "./dojo"

}, {

name: "dijit", location: "./dijit"

}, {

name: "dojox", location: "./dojox"

}, {

name: "wc", location: "./wc"

}, {

name: "fd/mobile", location: "./RAPIDStorefrontAssetStore/mobile/javascript/fd/mobile"

}

],

Please help us to understand how this needs to be resolved now. Thanks.

[brianlschultz]

So we thought the map was working, but it did not work when it came time for dojo to find classes in built js file. It was still loading individual js files.

[bill]

Surely a package name with a slash is asking for trouble, just like a directory name with a slash.

I don't understand what you are trying to do, but it seems like your package is actually "fd" and "mobile" is a directory within your package.

[trac-o-bot]

Because we get so many tickets, we often need to return them to the initial reporter for more information. If that person does not reply within 14 days, the ticket will automatically be closed, and that has happened in this case. If you still are interested in pursuing this issue, feel free to add a comment with the requested information and we will be happy to reopen the ticket if it is still valid. Thanks!