| Commit message (Collapse) | Author | Age | |
|---|---|---|---|
| * | External Libraries: Further fix jQuery deprecations in WordPress core. | Sergey Biryukov | 2021-03-18 |
| | | | | | | | | | | Follow-up to [50001], [50270], [50367], [50383], [50410], [50420], [50429]. Props Clorith. See #51812. git-svn-id: https://develop.svn.wordpress.org/trunk@50547 602fd350-edb4-49c9-b593-d223f7449a82 | ||
| * | External Libraries: First pass at fixing jQuery deprecations in WordPress ↵ | Sergey Biryukov | 2021-01-22 |
| | | | | | | | | | | | | | | | | | | core and bundled themes. To be able to disable jQuery Migrate as step 3 of updating the jQuery version shipped with WordPress, all `JQMIGRATE` warnings in the browser console will have to be addressed. This includes many minor adjustments to a wide array of core files. Follow-up to: * Step 1: Disabling jQuery Migrate 1.4.1 in WordPress 5.5: [48323], [48324] * Step 2: Updating jQuery to 3.5.1 and adding jQuery Migrate 3.3.x in WordPress 5.6: [49101], [49338], [49615], [49649] Props Clorith, azaozz. See #51812. git-svn-id: https://develop.svn.wordpress.org/trunk@50001 602fd350-edb4-49c9-b593-d223f7449a82 | ||
| * | I18N: Use `wp.i18n` for translatable strings in ↵ | Dominik Schilling | 2020-07-07 |
| | | | | | | | | | | | | | `wp-admin/js/inline-edit-post.js` and `wp-admin/js/inline-edit-tax.js`. This removes the usage of `wp_localize_script()` for passing translations to the scripts and instead adds the translatable strings in the scripts directly through the use of `wp.i18n` and its utilities. Props swissspidy, ocean90. See #20491. Fixes #50601. git-svn-id: https://develop.svn.wordpress.org/trunk@48391 602fd350-edb4-49c9-b593-d223f7449a82 | ||
| * | Docs: Improve inline comments per the documentation standards. | Sergey Biryukov | 2020-01-29 |
| | | | | | | | | | Includes minor code layout fixes for better readability. See #48303. git-svn-id: https://develop.svn.wordpress.org/trunk@47122 602fd350-edb4-49c9-b593-d223f7449a82 | ||
| * | Docs: Replace `@returns` tags in JS docs with `@return`. | Sergey Biryukov | 2019-11-29 |
| | | | | | | | | | | Per the documentation standards, `@returns` is an unsupported synonym, `@return` should be used instead: https://make.wordpress.org/core/handbook/best-practices/inline-documentation-standards/javascript/ See #48303. git-svn-id: https://develop.svn.wordpress.org/trunk@46800 602fd350-edb4-49c9-b593-d223f7449a82 | ||
| * | General: Explicitly assigns all JS globals to the window. | Omar Reiss | 2018-08-19 |
| | | | | | | | | | | Many variables in the JavaScript were defined in the global scope without being explicitly assigned to the window. When built with Webpack, the code gets encapsulated in anonymous functions and those implicit globals get assigned to the wrong scope. This patch prevents that from happening. Fixes #44371. See #43731. git-svn-id: https://develop.svn.wordpress.org/trunk@43577 602fd350-edb4-49c9-b593-d223f7449a82 | ||
| * | Docs: Add file doc `@output` annotations. | Anton Timmermans | 2018-06-15 |
| | | | | | | | | | | | | | | | | | | | These annotations make it clear to the reader of a JavaScript source where the build process outputs to. These annotations can later be integrated in a webpack configuration. This way there is one source of truth. The `build` folder is omitted from the paths, because a single JS file shouldn't not be responsible of knowing where outputs in general will end up at. A file only knows its output location relative to the project. Props adamsilverstein, herregroen, omarreiss, pento. Fixes #44361. git-svn-id: https://develop.svn.wordpress.org/trunk@43347 602fd350-edb4-49c9-b593-d223f7449a82 | ||
| * | Once upon a midnight dreary, while I coded, weak and weary, | Gary Pendergast | 2018-05-23 |
| In many a strange and curious file of forgotten lore— While I pondered, blaming Nacin, my notifications suddenly awakened, As of someone quietly DMing;—DMing me, I can’t ignore. “’Tis some contributor,” I muttered, “DMing me an idea or four— Only this and nothing more.” Ah, distinctly I remember, at WordCamp US, last December; A mad proposal nearly laid me—down out cold—upon the floor. Curious, I listened closely;—to a plan I agreed with, mostly— A way to make our JavaScript—JavaScript which was a chore— Maintainable, extendable, for the future, is what I saw. Guten-ready for evermore. Open here I switch to Slack, when, with many a patch and hack, In there stepped Omar, a JavaScript developer hardcore; Pronouncing all the changes fit; ready now to be commit; “There’s nothing else for us to do,” DMing me, “It’s done!” he swore— “No longer random guessing at which file need next be explored— Let’s move on, we’re all aboard.” Moved all together, grouped and managed, in folders all is packaged, The code had all been cleaned and tidied, important parts moved to the fore, “Though this change be useful here,” I said, “it is too large, I fear, We couldn’t manage such a patch, we’ve done nothing like this before— Tell me where doth go this change, change to make our codebase soar!” Quoth Omar, “In WordPress Core.” Props omarreis for shepherding this significant change. Props adamsilverstein, aduth, atimmer, dingo_bastard, frank-klein, gziolo, herregroen, jaswrks, jeremyfelt, jipmoors, jorbin, netweb, ocean90, pento, tjnowell, and youknowriad for testing, feedback, discussion, encouragement, commiserations, etc. I make no apologies for this commit message. Fixes #43055. git-svn-id: https://develop.svn.wordpress.org/trunk@43309 602fd350-edb4-49c9-b593-d223f7449a82 | |||
 |
index : wordpress | |
| WordPress | Aslak Raanes |
| summaryrefslogtreecommitdiffstatshomepage |