David Levine
@justlevine on WordPress.org and Slack
Bio
- Member Since: June 27th, 2011
- Website: axepress.dev
- GitHub: justlevine
- Job Title: Senior WordPress Engineer
- Employer: rtCamp
Contribution History
David Levine’s badges:- Core Contributor
- Plugin Developer
-
Mentioned in [59377] on Core SVN:
Coding Standards: Ensure cookie expiration value is an integer in `wp_update_user()`. -
Mentioned in [59376] on Core SVN:
Coding Standards: Remove unnecessary `isset()` from `xmlrpc.php`. -
Mentioned in [59373] on Core SVN:
Coding Standards: Ensure `$current` cookie time is `int` in `wp_user_settings()`. -
Mentioned in [59361] on Core SVN:
Editor: Correct the number of arguments for `WP_HTML_Tag_Processor::get_tag()`. -
Mentioned in [59357] on Core SVN:
Coding Standards: Use `WP_User_Query::get_results()` instead of a private property. -
Mentioned in [59343] on Core SVN:
Script Loader: Correct the number of arguments passed to `WP_Styles::get_etag()`. -
Submitted pull request #7723 to WordPress/wordpress-develop:
chore: remove unnecessary `isset()` from `xmlrpc.php` -
Submitted pull request #7721 to WordPress/wordpress-develop:
fix: ensure `$logged_in_cookie['expiration']` is `int` in `wp_update_user()` -
Submitted pull request #7720 to WordPress/wordpress-develop:
fix: incorrect array access to `template_name` property in `get_taxonomy_labels()` -
Submitted pull request #7719 to WordPress/wordpress-develop:
fix: ensure `$current` cookie time is `int` in `wp_user_settings()` -
Submitted pull request #7718 to WordPress/wordpress-develop:
fix: `WP_HTML_Tag_Processor::get_tag()` takes no parameter -
Submitted pull request #7716 to WordPress/wordpress-develop:
fix: use `WP_User_Query::get_results()` instead of private `::$results` property -
Mentioned in [59341] on Core SVN:
Script Loader: Correct the number of arguments passed to `WP_Styles::get_etag()`. -
Submitted pull request #7715 to WordPress/wordpress-develop:
fix: WP_Styles::get_etag() should only take `$load` parameter -
Mentioned in [59340] on Core SVN:
Coding Standards: Use explicit returns in `WP_Site_Health_Auto_Updates::test_*()`. -
Mentioned in [59337] on Core SVN:
Coding Standards: Explicitly return `false` in magic `__isset()` methods. -
Submitted pull request #66700 to WordPress/gutenberg:
fix: deprecated `WP_Webfonts()` constructor takes no arguments -
Submitted pull request #66699 to WordPress/gutenberg:
fix: remove extraneous arg from `gutenberg_url()` call in `gutenberg_posts_dashboard()` -
Submitted pull request #66698 to WordPress/gutenberg:
chore: remove unnecessary `isset()` in `_gutenberg_get_block_template_files()` -
Submitted pull request #66697 to WordPress/gutenberg:
fix: remove extraneous param from `remove_filter()` calls -
Submitted pull request #66696 to WordPress/gutenberg:
fix: explicitly return false in `WP_Theme_JSON_Gutenberg::should_override_preset()` -
Submitted pull request #66695 to WordPress/gutenberg:
chore: fix return type for `WP_Duotone_Gutenberg::get_selector()` -
Submitted pull request #66694 to WordPress/gutenberg:
fix: wrong number of `$accepted_args` on `add_filter()` calls -
Submitted pull request #66693 to WordPress/gutenberg:
Tools: Add and configure PHPStan static analysis -
Mentioned in [59336] on Core SVN:
Docs: Add missing `void` to DocBlock `@return` types. -
Mentioned in [59334] on Core SVN:
Docs: Correct `@param` type in `fix_phpmailer_messageid()`. -
Mentioned in [59333] on Core SVN:
Docs: Correct `@param` tag in `untrailingslashit()` to match the parameter name. -
Closed pull request #7684 on WordPress/wordpress-develop:
Chore: Remove invalid `@throws WP_Error` from `register_block_*()` doc-blocks -
Closed pull request #7674 on WordPress/wordpress-develop:
Fix: Explicitly return `null` instead of coercing voids in `WP_Navigation_Block_Renderer` -
Created issue #66598 in the WordPress/gutenberg repository:
Add PHPStan analysis -
Submitted pull request #7685 to WordPress/wordpress-develop:
chore: fix invalid `@var` type for `WP_HTML_Processor_State::$context_node` -
Submitted pull request #7684 to WordPress/wordpress-develop:
Chore: Remove invalid `@throws WP_Error` from `register_block_*()` doc-blocks -
Submitted pull request #7683 to WordPress/wordpress-develop:
Chore: cleanup incorrect method `@param`s -
Submitted pull request #7675 to WordPress/wordpress-develop:
Fix: use explicit returns in WP_Site_Health_Auto_Updates::test_*() methods -
Submitted pull request #7674 to WordPress/wordpress-develop:
Fix: Explicitly return `null` instead of coercing voids in `WP_Navigation_Block_Renderer` -
Submitted pull request #7673 to WordPress/wordpress-develop:
Fix: Explicitly return `false` in magic `__isset()` methods -
Submitted pull request #7672 to WordPress/wordpress-develop:
Chore: Add missing `void` to doc-blocks `return` types. -
Submitted pull request #7619 to WordPress/wordpress-develop:
Tests / Build Scripts: Configure PHPStan static analysis -
Completed the course How decisions are made in the WordPress project on learn.wordpress.org
-
Completed the course Open source basics and WordPress on learn.wordpress.org
-
Completed the course Open source basics and WordPress on learn.wordpress.org
-
Wrote a comment on the post JSX in WordPress 6.6, on the site Make WordPress Core:
This IMO should be part of the dev-note itself, and the dev-note should be added… -
Wrote a comment on the post How should we shape the future of the Plugin Review team?, on the site Make WordPress Plugins:
@talksina is the intent here to add Accessibility as a requirement to the [Plugin Guidelines](https://developer.wordpress.org/plugins/wordpress-org/detailed-plugin-guidelines/)… -
Wrote a comment on the post How should we shape the future of the Plugin Review team?, on the site Make WordPress Plugins:
> 3. Keeping track of popular plugins As @alanfuller and @yoancutillas both note, while periodic… -
Wrote a comment on the post Proposal to Update Our Event Venue Policy, on the site Make WordPress Community:
Agreed!! -
Mentioned in [58128] on Core SVN:
Upgrade/Install: Automatically roll back to the previous version when an automatic plugin update results in a fatal error on the front end of the site. -
Mentioned in [58083] on Core SVN:
Plugins: Show an admin notice on successful activation. -
Mentioned in [58081] on Core SVN:
Plugins: Show an admin notice on successful activation. -
Mentioned in [57985] on Core SVN:
General: Increase the minimum supported version of PHP to 7.2.24. -
Wrote a comment on the post Dropping support for PHP 7.0 and 7.1, on the site Make WordPress Core:
🥳🥳🥳 thanks @johnbillion for all the shepherding!
Contributor
-
WPGraphQL
Active Installs: 30,000+
Completed Courses
Total completed courses: 2
- How decisions are made in the WordPress project October 10, 2024
- Open source basics and WordPress October 10, 2024