Tide Chat Summary: April 27th
This post summarizes the Tide chat from April 27th in the #tide 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/. channel (agenda, Slack archive).
Reminder that the current Tide focus is integrating PHPPHP PHP (recursive acronym for PHP: Hypertext Preprocessor) is a widely-used open source general-purpose scripting language that is especially suited for web development and can be embedded into HTML. http://php.net/manual/en/intro-whatis.php. Compatibility data from Tide into WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/. Once PHP Compatibility is integrated into WordPress.org, we’ll assess the next focus to provide the biggest impact to the community.
Node refactoring
- @derekherman continues to progress towards a v1 launch of Tide refactored to use Node
- @antpb finished scoping out a complete rebuild of the PHP Compatibility Checker plugin, getting started on development phase and expects to begin integrating the Tide APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. in next two weeks but initial manual tests of endpoints looked positive
- @antpb planning for the pluginPlugin 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 to make an initial AJAX call to the endpoint to get the latest report / prime the report, considering hitting endpoint in a batch of ~100 at once
- Plugin currently has an option to check all active and inactive plugins, but @antpb may focus first on active plugins
- @jeffpaul suggested holding off the batch request until next plugin version to simplify initial refactor to using Tide API
- @antpb goal for plugin refactor is to look and perform exactly the same as the non-Tide API version, “with some personal opinionated changes sprinkled in” ✨
Automatically Catching Bugs in Plugins
- @jeffpaul shared plugin static code analysis post from @iandunn as “potential overlap with things Tide can help with”
- @jeffpaul stressed need to get Tide to a v1 with PHP Compat via Node refactor first, but from there looking to assist on @iandunn‘s concept could be a good next step
- @iandunn‘s main focus is building a consensus around what a Plugin Repository “standard” should include, likely more narrow than WPCSWPCS The collection of PHP_CodeSniffer rules (sniffs) used to format and validate PHP code developed for WordPress according to the WordPress Coding Standards. May also be an acronym referring to the Accessibility, PHP, JavaScript, CSS, HTML, etc. coding standards as published in the WordPress Coding Standards Handbook. and Tide, Psalm, but could definitely rely on them
Next meeting
The next meeting, a 30-minute Tide status update and open floor discussion, will take place on May 11, 2021 at 18:00 UTC in the #tide Slack channel. Please feel free to drop in with any updates or questions. If you have items to discuss but cannot make the meeting, please leave a comment on this post so that we can take them into account.