On Wed, Apr 25, 2012 at 5:29 AM, Drew Walters <deedu...@gmail.com> wrote: > I would agree that it shouldn't be "necessary" for the addPlugin API > (more like addNamespace), however it was nice to have during my > development. If you look at the addPlugin API you'll notice it waits > until DOMContentLoaded is fired so that the native browser globals > don't overwrite the plugin. It then calls a modified builder module > which handles overriding/merging in the various properties of the > plugin.
Seems like a docs issue more of an API surface issue to me. > Without addPlugin/mergePlugin there will certainly be repetition of > code and greater potential for plugins to unintentionally override > namespace of other plugins. could add those to util
