apiName config does not allow namespacing about curl HOT 4 CLOSED

hm. would this work?

var $namespace = {};
curl = { apiName: "require", apiContext: $namespace };

also:

curl = { apiName: "require", apiContext: window.$namespace };

The latter looks like a lot less code -- and/or a bit more end-user-dev flexibility. Thoughts?

from curl.

Yeah, that should do the trick. In either case the namespace will need to be constructed ahead of time (as per your first example), unless the loader initiated it if not defined (but I wouldn't expect that of a loader).

from curl.

Hi @asilvas! I'm committing a change on the dev branch that implements the apiContext option @unscriptable proposed. So, you'll be able to do any of:

var $namespace = {};
curl = { apiContext: $namespace } // $namespace.curl
// or
curl = { apiName: 'require', apiContext: $namespace } // $namespace.require
// and, of course
curl = { apiName: 'require' } // window.require

Hopefully, that works for what you need!

from curl.

Thanks, Brian!

from curl.