Have a topic for discussion for the next meeting? Leave a suggested edit on next week’s agenda.
Open Floor: Types in Gutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/
@aduth suggested to revisit the topic of improving types in Gutenberg. He mentions some work already done in URL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org module: https://github.com/WordPress/gutenberg/pull/17014
It was discussed to create a master issue with the progress of converting packages to use TypeScript validation based on JSDoc.
@gziolo fixed all ESLint warning related to the integration with the new plugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party which combines JSDoc and ESLint, however this probably needs to be further investigated.
- Create a tracking issue for module adoption of type checking
- Push forward on effort to improve docgen ability to understand more of the TypeScript-specific syntax
- Do some more conversions as demonstration
Open Floor: E2E Tests and Travis
Pushing a PR has been a bit of a chore recently with flakey tests, usually requiring a restart of a couple each time
For stability, it requires some diligence to investigate the underlying issues. Some improvements have been merged / proposed here:
@aduth have a few of these ideas in the Project Management Automation project board as well https://github.com/WordPress/gutenberg/projects/24
There was talk about documenting some of the common issues seen with E2E tests. Also to add a bot response with comments about the reasons of failing tests.
A CPU problem is mentioned: https://github.com/WordPress/gutenberg/pull/18770
- @noisysocks could look into some of this and write up findings/suggestions in an issue, not sure when though.