mirror of
https://github.com/inretio/WordPress-Plugin-Boilerplate
synced 2024-05-02 19:33:16 +03:00
5391e0ca27
Flattening the folder structure for a bit easier auto-inclusion into projects and local development. See: https://github.com/DevinVinson/WordPress-Plugin-Boilerplate/issues/295
33 lines
816 B
JavaScript
33 lines
816 B
JavaScript
(function( $ ) {
|
|
'use strict';
|
|
|
|
/**
|
|
* All of the code for your admin-specific JavaScript source
|
|
* should reside in this file.
|
|
*
|
|
* Note that this assume you're going to use jQuery, so it prepares
|
|
* the $ function reference to be used within the scope of this
|
|
* function.
|
|
*
|
|
* From here, you're able to define handlers for when the DOM is
|
|
* ready:
|
|
*
|
|
* $(function() {
|
|
*
|
|
* });
|
|
*
|
|
* Or when the window is loaded:
|
|
*
|
|
* $( window ).load(function() {
|
|
*
|
|
* });
|
|
*
|
|
* ...and so on.
|
|
*
|
|
* Remember that ideally, we should not attach any more than a single DOM-ready or window-load handler
|
|
* for any particular page. Though other scripts in WordPress core, other plugins, and other themes may
|
|
* be doing this, we should try to minimize doing that in our own work.
|
|
*/
|
|
|
|
})( jQuery );
|