1/** 2 * Public-facing JavaScript entry point for the MLSImport plugin. 3 * 4 * This is the WordPress plugin-boilerplate stub: a jQuery-wrapped IIFE reserved 5 * for general public-side scripting. It currently holds no behaviour â the 6 * standalone front-end features live in the dedicated `mlsimport-property-*.js` 7 * files. Kept as the conventional place to hang future public JS. 8 */ 9(function ( $ ) { 10 'use strict'; 11 12 /** 13 * All of the code for your public-facing JavaScript source 14 * should reside in this file. 15 * 16 * Note: It has been assumed you will write jQuery code here, so the 17 * $ function reference has been prepared for usage within the scope 18 * of this function. 19 * 20 * This enables you to define handlers, for when the DOM is ready: 21 * 22 * $(function() { 23 * 24 * }); 25 * 26 * When the window is loaded: 27 * 28 * $( window ).load(function() { 29 * 30 * }); 31 * 32 * ...and/or other possibilities. 33 * 34 * Ideally, it is not considered best practise to attach more than a 35 * single DOM-ready or window-load handler for a particular page. 36 * Although scripts in the WordPress core, Plugins and Themes may be 37 * practising this, we should strive to set a better example in our own work. 38 */ 39 40})( jQuery );
Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.