You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's fairly typical for methods that reset a library's namespace in order to avoid collision to be called noConflict. See jQuery, Underscore, Lodash, Bootstrap, and even mainly server-side libraries like node-uuid.
I think a setNamespace method is reserved for actually creating a new namespace on or from an object, not changing the object's current global namespace.
The text was updated successfully, but these errors were encountered:
It's fairly typical for methods that reset a library's namespace in order to avoid collision to be called
noConflict
. See jQuery, Underscore, Lodash, Bootstrap, and even mainly server-side libraries like node-uuid.I think a
setNamespace
method is reserved for actually creating a new namespace on or from an object, not changing the object's current global namespace.The text was updated successfully, but these errors were encountered: