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
Correctly implemented jquery plugins namespace their event handlers and data. This plugin does not. The names used when getting/setting data are supposed to be namespaced, by following the name with a dot and a namespace name. Also, when attaching event handlers, a dot and namespace should be appended.
The above examples use bootstrapselect as the "namespace" for the data and event handler.
This avoids trampling on any data that the user of the plugin has set on elements, inadvertently reading data set by the user of the plugin, facilitates removing only event handlers that have been added by the plugin, and prevents the user from accidentally wiping out event handlers added by the plugin.
Please see the jquery plugin developer's guide.
The text was updated successfully, but these errors were encountered:
I had started that some time ago, and some of the events that we trigger use a namespace.
We have chosen bs.select as the namespace for events. However, we haven't decided of an approach for the namespacing of the data because we have to mind existing code.
Correctly implemented jquery plugins namespace their event handlers and data. This plugin does not. The names used when getting/setting data are supposed to be namespaced, by following the name with a dot and a namespace name. Also, when attaching event handlers, a dot and namespace should be appended.
Examples:
The above examples use
bootstrapselect
as the "namespace" for the data and event handler.This avoids trampling on any data that the user of the plugin has set on elements, inadvertently reading data set by the user of the plugin, facilitates removing only event handlers that have been added by the plugin, and prevents the user from accidentally wiping out event handlers added by the plugin.
Please see the jquery plugin developer's guide.
The text was updated successfully, but these errors were encountered: