Have a topic for discussion for the next meeting? Leave a suggested edit on next week’s agenda.
Agenda: Should wp.hooks In WordPress theme and development, hooks are functions that can be applied to an action or a Filter in WordPress. Actions are functions performed when a certain event occurs in WordPress. Filters allow you to modify certain functions. Arguments used to hook both filters and actions look the same. support the special all hook?
In Gutenberg#8602 it is raised if we should add support for an
all action in wp.hooks in order to match feature parity with the current PHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher hooks system in WordPress core Core is the set of software required to run WordPress. The Core Development Team builds WordPress.. While there were no real objections raised in the chat, pretty much everyone present agreed with this comment:
If it is primarily intended for debugging, then it might be worth exploring optimizations to avoid any impact in typical usage, e.g. monkey-patching @aduth
runHooks when an
all hook is added.
- No interest was expressed in the issue. If anyone wants to take it on, there wouldn’t be any objections either.
Agenda: Ways to optimize the package updating process
This problem would probably not exist once everything is merged into a single monorepo hosted on git. But that doesn’t seem feasible just yet. Could we maybe mimic the advantage of having a monorepo a bit by getting more tooling into WordPress core and build straight from Github GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ source? That would at least decouple publication of packages from being able to consume their changes in WordPress core development.
It was raised by @gziolo that installing Gutenberg straight from Github with npm is not an option because Gutenberg consumes local packages which can’t be resolved by npm. The solution proposed is to take a similar approach to how Gutenberg packages are updated for Drupal.
This is done with an install script that simply clones Gutenberg into node_modules and builds the scripts in Gutenberg itself. While not a very elegant solution, this could work and drastically improve the process of keeping the packages updated.
- @atimmer will work on a proof of concept.