Tide Chat Summary: February 16th

This post summarizes the Tide chat from February 16th 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 still has some items left on his todo list, but is aiming for an RC1 release as early as March 2nd
  • Latest improvements was code coverage going from ~30% to ~94%, refactoring logic post proof-of-concept stage, and adding proper error handling
  • A new Cloud Function was added to host the Swagger UIUI UI is an acronym for User Interface - the layout of the page the user interacts with. Think ‘how are they doing that’ and less about what they are doing. so you can now interact with the API in the browser
  • @derekherman met with folks at WP Engine last week to discuss 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. as a data source for the PHP Compatibility Checker plugin that they support, the result of the meeting can be found on a related support forum post from @antpb
  • PHPCS reports are now separated by PHP version to make it easier to build a UI on top of. These can be viewed in the PHPCS schema object
  • Tide now stores not just 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/theme version being audited, but also the version of the report (e.g., PHPCS) that the audit relates to in the Dependencies object, that’s part of the Report object, that’s part of the Audit object (where the plugin/theme version resides)
  • The API stores info about the server including Node and PHP version as well as the package used to run the audit
  • @derekherman is considering switching from Datastore to Firestore as a breaking change headed into an RC1 as this would allow a status UI as a VueVue Vue (pronounced /vjuː/, like view) is a progressive framework for building user interfaces. https://vuejs.org/. component in the docs to see audits in realtime, more details to come on that in the next Tidechat
  • @antpb to share test results as the PHP Compatibility Checker team gets further along in their development process
  • Biggest help others can provide is to test the Node version locally from https://staging.wptide.org/ and highlight any issues found as a GitHub issue, comment in Slack, or as a comment on this post

Next meeting

The next meeting, a 30-minute Tide status update and open floor discussion, will take place on March 2, 2021 at 19: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.

#summary, #tide-chat