luisherranz
@luisherranz on WordPress.org and Slack
Bio
Contributions
- Member Since: October 6th, 2015
- Location: Madrid
- GitHub: luisherranz
- Job Title: Code Wrangler
- Employer: Automattic
Contribution History
luisherranz’s badges:- Core Contributor
- Core Team
- Documentation Contributor
- Plugin Developer
- WordCamp Speaker
-
Merged pull request #76151 into WordPress/gutenberg:
Interactivity: Fix crypto.randomUUID crash in non-secure contexts -
Merged pull request #76191 into WordPress/gutenberg:
Merge cherry-pick conflicts for PR 76053 in the wp/7.0 branch -
Submitted pull request #76191 to WordPress/gutenberg:
Merge cherry-pick conflicts for PR 76053 in the wp/7.0 branch -
Merged pull request #76053 into WordPress/gutenberg:
Interactivity API: Fix router initialization race condition on Safari/Firefox -
Wrote a new post, Changes to the Interactivity API in WordPress 7.0, on the site Make WordPress Core:
New watch() function WordPress 7.0 introduces a watch() function in the @wordpress/interactivity package. It subscribes… -
Merged pull request #75263 into WordPress/gutenberg:
iAPI Docs: Add client-side navigation guide under "Core Concepts" -
Submitted pull request #25 to WordPress/agent-skills:
Add CODEOWNERS and designate `@WordPress/interactivity-api` as the code owners of the `wp-interactivity-api`... -
Submitted pull request #24 to WordPress/agent-skills:
Block development: static vs dynamic blocks -
Pull request #75357 merged into WordPress/gutenberg:
iAPI Docs: Introduce reactive vs non-reactive distinction early in the state/context guide -
Closed issue #75827 on the WordPress/gutenberg repository:
Docs: wrong use of wp_interactivity_state? -
Pull request #75680 merged into WordPress/gutenberg:
Gallery: Skip interactivity directives when no images have lightbox enabled -
Submitted pull request #75680 to WordPress/gutenberg:
Gallery: Skip interactivity directives when no images have lightbox enabled -
Closed ticket #64649 on Core Trac:
Interactivity API: Initialize router's `state.url` on the server -
Committed [61659] to Core SVN:
Interactivity API: populate router's `state.url` in the server Set ... -
Closed issue #70879 on the WordPress/gutenberg repository:
iAPI router: Move internal properties to a private store -
Merged pull request #70882 into WordPress/gutenberg:
iAPI router: Move internal properties to a private store -
Closed ticket #64647 on Core Trac:
Interactivity API: Update loading bar to use private router store -
Committed [61653] to Core SVN:
Interactivity API: Use the private router store for the loading bar ... -
Merged pull request #75563 into WordPress/gutenberg:
Interactivity API: Export `watch` from `@preact/signals`'s `effect` -
Submitted pull request #10944 to WordPress/wordpress-develop:
Interactivity API: populate router's `state.url` in the server -
Created ticket #64649 on Core Trac:
Interactivity API: Initialize router's `state.url` on the server -
Submitted pull request #10942 to WordPress/wordpress-develop:
Interactivity API: Update loading bar to use private router store -
Created ticket #64647 on Core Trac:
Interactivity API: Update loading bar to use private router store -
Submitted pull request #75563 to WordPress/gutenberg:
Interactivity API: Export `watch` from `@preact/signals`'s `effect` -
Closed pull request #75514 on WordPress/gutenberg:
[WIP] Introduce reactive vs non-reactive distinction in state/context guide -
Closed pull request #75480 on WordPress/gutenberg:
iAPI Docs: Fix typo in "Understanding global state, local context, and derived... -
Merged pull request #75512 into WordPress/gutenberg:
Update manifest.json and toc.json for renamed state/context guide -
Closed pull request #75477 on WordPress/gutenberg:
[WIP] Introduce reactive vs non-reactive distinction in state guide -
Merged pull request #75473 into WordPress/gutenberg:
Rename state/context guide to include config in title and filename -
Merged pull request #75097 into WordPress/gutenberg:
iAPI Router: Update cached styles for re-fetched pages -
Submitted pull request #75357 to WordPress/gutenberg:
iAPI Docs: Introduce reactive vs non-reactive distinction early in the state/context guide -
Pull request #71355 merged into WordPress/gutenberg:
iAPI Docs: add config to state/context guide -
Merged pull request #74857 into WordPress/gutenberg:
iAPI Router: Fix initial router regions with `attachTo` being duplicated after `navigate()` -
Merged pull request #74750 into WordPress/gutenberg:
iAPI Router: Prevent router regions with `data-wp-key` from being recreated on navigation -
Closed issue #74685 on the WordPress/gutenberg repository:
Image block: The page is prevented from scrolling after the lightbox is... -
Closed issue #74184 on the WordPress/gutenberg repository:
Image block “Enlarge on click” throws JS error and locks page scrolling... -
Closed issue #70870 on the WordPress/gutenberg repository:
iAPI: Review the initialization logic -
Merged pull request #71123 into WordPress/gutenberg:
iAPI: Fix and refactor runtime initialization logic -
Submitted pull request #10746 to WordPress/wordpress-develop:
Interactivity API: Fix `data-wp-bind` to continue processing valid directives after encountering invalid... -
Created ticket #64518 on Core Trac:
Interactivity API: `data-wp-bind` stops processing valid directives ... -
Mentioned in [61471] on WordPress SVN:
Twenty Twenty-One: Only enqueue block editor assets in the admin. -
Closed issue #74148 on the WordPress/gutenberg repository:
Details element missing open attribute after enhancement pagination content update -
Submitted pull request #74446 to WordPress/gutenberg:
iAPI: Preserve boolean HTML attributes during client side navigation -
Submitted pull request #73540 to WordPress/gutenberg:
iAPI: Fix using getServerContext in derived state getters (using signals) -
Pull request #73531 merged into WordPress/gutenberg:
iAPI: Backport of "Fix using getServerContext in derived state getters" -
Submitted pull request #73531 to WordPress/gutenberg:
iAPI: Backport of "Fix using getServerContext in derived state getters" -
Merged pull request #73518 into WordPress/gutenberg:
iAPI: Fix using `getServerContext` in derived state getters -
Merged pull request #73514 into WordPress/gutenberg:
iAPI: Backport of "Return a deep-clone object from `getServerState` and `getServerContext` functions" -
Submitted pull request #73518 to WordPress/gutenberg:
iAPI: Fix using `getServerContext` in derived state getters -
Submitted pull request #73514 to WordPress/gutenberg:
iAPI: Backport of "Return a deep-clone object from `getServerState` and `getServerContext` functions"
Contributor
-
REST API - Head Tags
Active Installs: 200+
Completed Courses
Total completed courses: 3
- How decisions are made in the WordPress project July 18, 2022
- Community meeting etiquette September 27, 2021
- Open source basics and WordPress September 24, 2021
