David Arenas
@darerodz on WordPress.org and Slack
Bio
Contributions
- Member Since: February 9th, 2021
- GitHub: DAreRodz
- Job Title: Software Engineer
- Employer: Automattic
Contribution History
David Arenas’s badges:- Core Contributor
-
Submitted pull request #73437 to WordPress/gutenberg:
iAPI: Return a deep-clone object from `getServerState` and `getServerContext` functions -
Wrote a new post, Changes to the Interactivity API in WordPress 6.9, on the site Make WordPress Core:
Standardized API to set unique IDs in directives HTML does not allow multiple attributes with… -
Wrote a new post, Interactivity API’s client navigation improvements in WordPress 6.9, on the site Make WordPress Core:
In WordPress 6.9, the client-side navigation feature provided by the @wordpress/interactivity-router module has been expanded… -
Mentioned in [61197] on WordPress SVN:
Interactivity API: Fatal error processing incorrect closed tags. -
Submitted pull request #73147 to WordPress/gutenberg:
iAPI Router: Show warning message for missing `data-wp-interactive` in router regions -
Pull request #72977 merged into WordPress/gutenberg:
Accordion block: Lock `core/accordion` iAPI store -
Submitted pull request #72977 to WordPress/gutenberg:
Accordion block: Lock `core/accordion` iAPI store -
Closed issue #71722 on the WordPress/gutenberg repository:
[Flaky Test] should refresh the page when stylesheet loading fails -
Merged pull request #72783 into WordPress/gutenberg:
Tests: Try fixing "should refresh the page when stylesheet loading fails" e2e... -
Submitted pull request #72783 to WordPress/gutenberg:
Tests: Try fixing "should refresh the page when stylesheet loading fails" e2e... -
Pull request #72715 merged into WordPress/gutenberg:
Image block: Add guard for `null` refs in `setButtonStyles` callback -
Pull request #72725 merged into WordPress/gutenberg:
iAPI: Fix derived state closures processing on client-side navigation -
Submitted pull request #72725 to WordPress/gutenberg:
iAPI: Fix derived state closures processing on client-side navigation -
Submitted pull request #72715 to WordPress/gutenberg:
Image block: Add guard for `null` refs in `setButtonStyles` callback -
Mentioned in [61020] on WordPress SVN:
Interactivity API: Support unique IDs in server-side directives processing. -
Closed issue #70866 on the WordPress/gutenberg repository:
iAPI: Items from `data-wp-each` doesn't work when exposed from state getters -
Merged pull request #70424 into WordPress/gutenberg:
iAPI: Fix `wp-each` item contexts for objects with same key -
Closed issue #70872 on the WordPress/gutenberg repository:
iAPI router: Support lazy loaded derived state -
Mentioned in [60953] on WordPress SVN:
Interactivity API: Support lazy-loaded derived state props. -
Closed issue #70873 on the WordPress/gutenberg repository:
iAPI Router: Only load modules of interactive blocks on client-side navigation -
Merged pull request #72340 into WordPress/gutenberg:
iAPI Router: Selectively preload interactivity script modules -
Closed issue #71722 on the WordPress/gutenberg repository:
[Flaky Test] should refresh the page when stylesheet loading fails -
Merged pull request #72329 into WordPress/gutenberg:
Try: Fix flaky router styles e2e tests -
Merged pull request #72164 into WordPress/gutenberg:
Changelogs: Fix example to match standard format -
Submitted pull request #72164 to WordPress/gutenberg:
Changelogs: Fix example to match standard format -
Pull request #72038 merged into WordPress/gutenberg:
iAPI: Add missing changelog entries for #71870 and #71635 PRs -
Submitted pull request #72038 to WordPress/gutenberg:
iAPI: Add missing changelog entries for #71870 and #71635 PRs -
Pull request #71635 merged into WordPress/gutenberg:
iAPI Router: Update router regions inside elements with `data-wp-interactive` -
Merged pull request #71870 into WordPress/gutenberg:
iAPI: Fix nested `data-wp-each` directives using the same items key -
Submitted pull request #71870 to WordPress/gutenberg:
iAPI: Fix nested `data-wp-each` directives using the same items key -
Submitted pull request #71635 to WordPress/gutenberg:
iAPI Router: Update router regions inside elements with `data-wp-interactive` -
Created issue #71519 in the WordPress/gutenberg repository:
iAPI Router: Support router regions nested inside `data-wp-interactive` elements -
Submitted pull request #9673 to WordPress/wordpress-develop:
Interactivity API: Add support for lazy-loaded derived state props -
Created ticket #63898 on Core Trac:
Add support for lazy-loaded derived state props -
Closed issue #70874 on the WordPress/gutenberg repository:
iAPI router: Synchronous getter execution prevents `state` access when store is initialized... -
Merged pull request #70974 into WordPress/gutenberg:
iAPI: Make state getters to be updated asynchronously with `store()` -
Submitted pull request #71125 to WordPress/gutenberg:
iAPI: Skip directive execution for "lazy" derived state props -
Submitted pull request #71123 to WordPress/gutenberg:
iAPI: Refactor runtime initialization logic -
Closed issue #70876 on the WordPress/gutenberg repository:
iAPI Router: Styles inside `noscript` tags are wrongly applied on client-side navigation -
Merged pull request #70905 into WordPress/gutenberg:
iAPI Router: Ignores `` elements while preparing DOM. -
Submitted pull request #70974 to WordPress/gutenberg:
iAPI: Make state getters to be updated asynchronously with `store()` -
Closed issue #70881 on the WordPress/gutenberg repository:
iAPI: Deprecate `data-wp-ignore` -
Merged pull request #70945 into WordPress/gutenberg:
Deprecate data-wp-ignore directive with warning message -
Closed issue #67276 on the WordPress/gutenberg repository:
Interactivity API iteration for WordPress 6.8 -
Created issue #70883 in the WordPress/gutenberg repository:
Interactivity API iteration for WordPress 6.9 -
Created issue #70881 in the WordPress/gutenberg repository:
iAPI: Deprecate `data-wp-ignore` -
Created issue #70878 in the WordPress/gutenberg repository:
iAPI: Implement a `data-wp-if` directive -
Created issue #70876 in the WordPress/gutenberg repository:
iAPI Router: Styles inside `noscript` tags are wrongly applied on client-side navigation -
Created issue #70875 in the WordPress/gutenberg repository:
iAPI router: Add an `isRouterRegion` property in `block.json` for automatic incompatible blocks... -
Created issue #70873 in the WordPress/gutenberg repository:
iAPI Router: Only load modules of interactive blocks on client-side navigation