Skip to content

Conversation

simison
Copy link
Member

@simison simison commented Sep 16, 2025

Resolves FORMS-287

Alternative to #45169

Proposed changes:

  • Adds util pulling a version from the generated view.asset.php file, falling back to Jetpack version
  • Use the new util in all iAPI modules for Forms

Before

Screenshot 2025-09-16 at 13 44 38

After

Screenshot 2025-09-16 at 13 43 49

Other information:

  • Have you written new tests for your changes, if applicable?
  • Have you checked the E2E test CI results, and verified that your changes do not break them?
  • Have you tested your changes on WordPress.com, if applicable (if so, you'll see a generated comment below with a script to run)?

Jetpack product discussion

Does this pull request change what data or activity we track or use?

Testing instructions:

  • Test forms frontend, check that file gets cache-busted with the hash found in the generated view.asset.php files
  • Test multi step forms
  • Test slider, rating, file upload, and phone fields

@simison simison requested a review from a team September 16, 2025 10:45
@simison simison added [Status] Needs Review This PR is ready for review. [Package] Forms [Feature] Forms Blocks Blocks designed to streamline user input and engagement, such as contact, newsletter sign-ups, etc. labels Sep 16, 2025
Copy link
Contributor

github-actions bot commented Sep 16, 2025

Are you an Automattician? Please test your changes on all WordPress.com environments to help mitigate accidental explosions.

  • To test on WoA, go to the Plugins menu on a WoA dev site. Click on the "Upload" button and follow the upgrade flow to be able to upload, install, and activate the Jetpack Beta plugin. Once the plugin is active, go to Jetpack > Jetpack Beta, select your plugin (Jetpack), and enable the update/forms-version-modules-with-asset-file branch.
  • To test on Simple, run the following command on your sandbox:
bin/jetpack-downloader test jetpack update/forms-version-modules-with-asset-file

Interested in more tips and information?

  • In your local development environment, use the jetpack rsync command to sync your changes to a WoA dev blog.
  • Read more about our development workflow here: PCYsg-eg0-p2
  • Figure out when your changes will be shipped to customers here: PCYsg-eg5-p2

Copy link
Contributor

github-actions bot commented Sep 16, 2025

Thank you for your PR!

When contributing to Jetpack, we have a few suggestions that can help us test and review your patch:

  • ✅ Include a description of your PR changes.
  • ✅ Add a "[Status]" label (In Progress, Needs Review, ...).
  • ✅ Add a "[Type]" label (Bug, Enhancement, Janitorial, Task).
  • ✅ Add testing instructions.
  • ✅ Specify whether this PR includes any changes to data or privacy.
  • ✅ Add changelog entries to affected projects

This comment will be updated as you work on your PR and make changes. If you think that some of those checks are not needed for your PR, please explain why you think so. Thanks for cooperation 🤖


Follow this PR Review Process:

  1. Ensure all required checks appearing at the bottom of this PR are passing.
  2. Make sure to test your changes on all platforms that it applies to. You're responsible for the quality of the code you ship.
  3. You can use GitHub's Reviewers functionality to request a review.
  4. When it's reviewed and merged, you will be pinged in Slack to deploy the changes to WordPress.com simple once the build is done.

If you have questions about anything, reach out in #jetpack-developers for guidance!

@github-actions github-actions bot added [Feature] Contact Form [Status] Needs Author Reply We need more details from you. This label will be auto-added until the PR meets all requirements. and removed [Status] Needs Review This PR is ready for review. labels Sep 16, 2025
Copy link

jp-launch-control bot commented Sep 16, 2025

Code Coverage Summary

Coverage changed in 4 files.

File Coverage Δ% Δ Uncovered
projects/packages/forms/src/contact-form/class-contact-form-field.php 1075/1679 (64.03%) -0.12% 2 ❤️‍🩹
projects/packages/forms/src/contact-form/class-util.php 42/170 (24.71%) 1.68% 1 ❤️‍🩹
projects/packages/forms/src/contact-form/class-contact-form-plugin.php 424/1302 (32.57%) 0.07% -3 💚
projects/packages/forms/src/contact-form/class-contact-form.php 585/1090 (53.67%) 0.15% -3 💚

Full summary · PHP report · JS report

@simison simison added [Type] Enhancement Changes to an existing feature — removing, adding, or changing parts of it [Status] Needs Review This PR is ready for review. and removed [Status] Needs Author Reply We need more details from you. This label will be auto-added until the PR meets all requirements. labels Sep 16, 2025
* @param string $asset_file Path to view.asset.php file.
* @return string either asset hash or Jetpack version.
*/
public static function get_view_asset_version( $asset_file ) {
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I could see this in Jetpack main plugin's Assets package as well.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why view in the method name? Won't it work for any assets.php file?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yep! It does.

I'm thinking of renaming to better highlight the intent of using alongside wp_enqueue_script_module(). Or just leave it generic.

*/
public static function get_view_asset_version( $asset_file ) {
$asset = file_exists( $asset_file ) ? require $asset_file : null;
$jetpack_version = Constants::get_constant( 'JETPACK__VERSION' );
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Alternatively we could fail loudly instead of falling back to JP version; now if the path is incorrect for example, dev might not notice.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Failing when we actually expect the file to exist is better IMHO.

@simison simison force-pushed the update/forms-version-modules-with-asset-file branch from 5d96c9b to 363abbe Compare September 16, 2025 11:25
Co-authored-by: Manzoor Wani <manzoorwani.jk@gmail.com>
@simison
Copy link
Member Author

simison commented Sep 16, 2025

Another consideration; in earlier PR we had used similar generated version for each asset, but we really need it only for modules. Should we use it everywhere or just focus on fields with modules?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Feature] Contact Form [Feature] Forms Blocks Blocks designed to streamline user input and engagement, such as contact, newsletter sign-ups, etc. [Package] Forms [Status] Needs Review This PR is ready for review. [Type] Enhancement Changes to an existing feature — removing, adding, or changing parts of it
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants