luisherranz
@luisherranz on WordPress.org and Slack
Bio
Contributions Sponsored
- Member Since: October 6th, 2015
- Location: Madrid
- GitHub: luisherranz
- Job Title: Code Wrangler
- Employer: Automattic
Contribution History
luisherranz’s badges:- Core Contributor
- Plugin Developer
- WordCamp Speaker
-
Mentioned in [57843] on Core SVN:
Interactivity API: Do not print state if it’s an empty array. -
Mentioned in [57841] on Core SVN:
Interactivity API: Do not print state if it’s an empty array. -
Mentioned in [57834] on Core SVN:
Interactivity API: Do not propagate context from void tags to its siblings. -
Mentioned in [57832] on Core SVN:
Interactivity API: Do not propagate context from void tags to its siblings. -
Mentioned in [57762] on Core SVN:
Interactivity API: Rename `data_wp_context()` to `wp_interactivity_data_wp_context()`. -
Mentioned in [57742] on Core SVN:
Interactivity API: Rename `data_wp_context()` to `wp_interactivity_data_wp_context()`. -
Merged pull request #58864 into WordPress/gutenberg:
Interactivity API: Limit the exported APIs -
Merged pull request #58835 into WordPress/gutenberg:
Image block: refactor and remove `data-wp-body` -
Pull request #58846 merged into WordPress/gutenberg:
Interactivity API: use compat versions of HTML APIs -
Submitted pull request #58846 to WordPress/gutenberg:
Interactivity API: use compat versions of HTML APIs -
Submitted pull request #58835 to WordPress/gutenberg:
Image block: refactor and remove `data-wp-body` -
Closed issue #58823 on the WordPress/gutenberg repository:
Decide what `preact`, `preact/hooks`, `@preact/signals` and `deepsignal` APIs we should reexport -
Created issue #58823 in the WordPress/gutenberg repository:
Decide what `preact`, `preact/hooks`, `@preact/signals` and `deepsignal` APIs we should reexport -
Mentioned in [57565] on Core SVN:
Editor: Add `viewScriptModule` handling to `block.json` metadata -
Mentioned in [57563] on Core SVN:
Interactivity API: Integrate Server Directive Processing -
Merged pull request #58678 into WordPress/gutenberg:
Interactivity API - Blocks: Move interactivity registration to render -
Merged pull request #58743 into WordPress/gutenberg:
Interactivity API: Support setting a namespace using a string in `data-wp-interactive` -
Mentioned in [57545] on Core SVN:
Upgrade/Install: Introduce Plugin Dependencies. -
Submitted pull request #58743 to WordPress/gutenberg:
Interactivity API: Support setting a namespace using a string in `data-wp-interactive` -
Closed issue #58398 on the WordPress/gutenberg repository:
[Flaky Test] callbacks should run whenever the specified event is dispatched -
Merged pull request #58498 into WordPress/gutenberg:
Interactivity API: Server Directive Processor for `data-wp-each` -
Merged pull request #58496 into WordPress/gutenberg:
Interactivity Router: Fix initial page cache -
Closed issue #58398 on the WordPress/gutenberg repository:
[Flaky Test] callbacks should run whenever the specified event is dispatched -
Submitted pull request #58642 to WordPress/gutenberg:
Fix flaky test of data-wp-on-window directive -
Closed issue #58332 on the WordPress/gutenberg repository:
[Flaky Test] directives inside islands should not be hydrated twice -
Merged pull request #58516 into WordPress/gutenberg:
Flaky Test: Fix "directives inside islands should not be hydrated twice" -
Mentioned in [57503] on Core SVN:
Script Loader: Use a global variable in `wp_script_modules()`. -
Submitted pull request #58498 to WordPress/gutenberg:
Interactivity API: Server Directive Processor for `data-wp-each` -
Mentioned in [57499] on Core SVN:
Editor: Update WordPress packages to Gutenberg 16.7 RC3. -
Mentioned in [57492] on Core SVN:
Script Modules API: Add import map polyfill for older browsers -
Mentioned in [57377] on Core SVN:
Editor: Update the WordPress packages to the Gutenberg 16.7 RC2 version. -
Closed ticket #60232 on Core Trac:
Script Modules API: Add import map polyfill -
Submitted pull request #5953 to WordPress/wordpress-develop:
Interactivity API: Server Directive Processing -
Created ticket #60356 on Core Trac:
Interactivity API: Server Directive Processing -
Merged pull request #58316 into WordPress/gutenberg:
Interactivity API: Add `supports.interactivity` to the Query block -
Submitted pull request #58316 to WordPress/gutenberg:
Interactivity API: Add `supports.interactivity` to the Query block -
Pull request #58242 merged into WordPress/gutenberg:
Prevent usage of `gutenberg_url` in block-library -
Submitted pull request #58242 to WordPress/gutenberg:
Prevent usage of `gutenberg_url` in block-library -
Merged pull request #57924 into WordPress/gutenberg:
Interactivity API: Create `@wordpress/interactivity-router` module -
Mentioned in [57346] on Core SVN:
Editor: update npm packages in trunk for 6.4.3. -
Merged pull request #58066 into WordPress/gutenberg:
Interactivity API: Server Directive Processing Refactor -
Closed issue #57983 on the WordPress/gutenberg repository:
[Flaky Test] the event listener is removed when the element is removed -
Merged pull request #58181 into WordPress/gutenberg:
Interactivity API: Fix flaky test on-window, remove duplicate expect on-document. -
Mentioned in [57345] on Core SVN:
Script Loader: Load the modules to the footer in classic themes -
Closed issue #57983 on the WordPress/gutenberg repository:
[Flaky Test] the event listener is removed when the element is removed -
Merged pull request #58134 into WordPress/gutenberg:
Interactivity API: Fix flaky test on-window -
Closed issue #57983 on the WordPress/gutenberg repository:
[Flaky Test] the event listener is removed when the element is removed -
Merged pull request #58008 into WordPress/gutenberg:
Interactivity API: Fix data-wp-on-document flaky test -
Submitted pull request #5931 to WordPress/wordpress-develop:
Script Modules API: Move the script modules to the footer in classic... -
Mentioned in [57327] on Core SVN:
Script Modules API: Rename `wp_module` to `wp_script_module`
Contributor
-
REST API - Head Tags
Active Installs: 400+