Skip to content

Commit b88d135

Browse files
committed
Advanced Plugin Concepts: Changed "Firebug console" to "console"
Closes jquerygh-453
1 parent ba4f586 commit b88d135

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

page/plugins/advanced-plugin-concepts.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -110,7 +110,7 @@ This technique makes it possible for others to define and ship transition defini
110110

111111
The technique of exposing part of your plugin to be overridden can be very powerful. But you need to think carefully about what parts of your implementation to expose. Once it's exposed, you need to keep in mind that any changes to the calling arguments or semantics may break backward compatibility. As a general rule, if you're not sure whether to expose a particular function, then you probably shouldn't.
112112

113-
So how then do we define more functions without cluttering the namespace and without exposing the implementation? This is a job for closures. To demonstrate, we'll add another function to our plugin called "debug". The debug function will log the number of selected elements to the Firebug console. To create a closure, we wrap the entire plugin definition in a function (as detailed in the jQuery Authoring Guidelines).
113+
So how then do we define more functions without cluttering the namespace and without exposing the implementation? This is a job for closures. To demonstrate, we'll add another function to our plugin called "debug". The debug function will log the number of selected elements to the console. To create a closure, we wrap the entire plugin definition in a function (as detailed in the jQuery Authoring Guidelines).
114114

115115
```
116116
// Create closure.

0 commit comments

Comments
 (0)