Editor Chat Agenda: August 21st

Welcome!

The WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. development team builds WordPress! Follow this site for general updates, status reports, and the occasional code debate. There’s lots of ways to contribute:

Found a bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority.? Create a ticket in the bug tracker.
Want to contribute? Get started quickly with tickets marked as good first bugs for new contributors or join a bug scrub. There’s more on the reports page, like patches needing testing, and on feature projects page.
Other questions? Here is a detailed handbook for contributors, complete with tutorials.

Note taker: @nosolosw

This is the agenda for the weekly editor chat scheduled for August 21, 2019 at 1300 UTC.

This meeting is held in the #core-editor channel in the Making WordPress SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/..

Tasks Coordination
Open Floor

If you have anything to share for the Tasks Coordination section, please leave it as a comment on this post.

As always, if you have anything to propose for the agenda or other specific items related to those listed above, please leave a comment below.

#agenda, #core-editor, #editor-chat

Darren Ethier (nerrad) 2:46 pm on August 20, 2019

I opened a pull over the weekend where I’ve started going through the `wordpress/components` package with an eye towards identifying components in the package that might be good candidates for extraction into either their own package or a separate bundled package usable in more contexts: https://github.com/WordPress/gutenberg/issues/17079

The goal is to reduce the weight of `wordpress/components`, keep it’s contents specific to _just_ the editor/adminadmin (and super admin) context and curate more targeted packages for potential inclusion in other contexts (frontend etc).

While the issue is still a work in progress, I welcome feedback on whether it’s something worth pursuing and what I’ve identified so far as candidates.
tellthemachines 9:06 am on August 21, 2019

I’ve been noticing an issue with the e2e tests when markup changes are made to a coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience.. Even if there’s a deprecation in place and deprecated instances of the block are working fine, there are a bunch of `console.warning`s coming from `packages/blocks/src/api/validation.js` that cause `packages/e2e-tests/specs/demo.test.js` to fail. The test itself would not fail if those warnings were not being output. I have created an issue for this: https://github.com/WordPress/gutenberg/issues/17003 and would love to know people’s thoughts on changing this so that the tests _don’t_ fail just because of a console warning.
I think (correct me if I’m wrong) previously this issue has been dealt with by updating the blocks in the demo post, which doesn’t seem awfully efficient.

Comments are closed.

Welcome!

Communication

Share this: