Skip to content

Conversation

@CGastrell
Copy link
Contributor

Proposed changes:

This PR removes Dashboard_View_Switch class, which has been in deprecation since moving towards the new dashboard and removal of the legacy menu/listing.

This shouldn't be mixed with current proposal to deprecate Admin class, which carries more legacy and backwards compatibility checks.

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

None yet, but there will be

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

No

Testing instructions:

As with any removal, the idea is that nothing has changed and tests pass. Special attention to any of the tasks in charge of Dashboard View Switch, although most of them had been deprecated via conditionals based on flags that are now set to default values that never make it through those conditionals.

Also, moved some of the useful methods on the class to static methods on Dashboard:

  • get_forms_admin_url
  • append_tab_to_url
  • is_jetpack_forms_admin_page

@CGastrell CGastrell self-assigned this Sep 23, 2025
@CGastrell CGastrell added [Status] Needs Review This PR is ready for review. [Type] Janitorial [Plugin] Jetpack Issues about the Jetpack plugin. https://wordpress.org/plugins/jetpack/ [Package] Forms Coverage tests to be added later Use to ignore the Code coverage requirement check when tests will be added in a follow-up PR labels Sep 23, 2025
@github-actions
Copy link
Contributor

github-actions bot commented Sep 23, 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 remove/forms-dashboard-switch-class branch.
  • To test on Simple, run the following command on your sandbox:
bin/jetpack-downloader test jetpack remove/forms-dashboard-switch-class

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

@github-actions
Copy link
Contributor

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!


Jetpack plugin:

The Jetpack plugin has different release cadences depending on the platform:

  • WordPress.com Simple releases happen as soon as you deploy your changes after merging this PR (PCYsg-Jjm-p2).
  • WoA releases happen weekly.
  • Releases to self-hosted sites happen monthly:
    • Scheduled release: October 7, 2025
    • Code freeze: October 6, 2025

If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack.

@jp-launch-control
Copy link

jp-launch-control bot commented Sep 23, 2025

Code Coverage Summary

Coverage changed in 8 files. Only the first 5 are listed here.

File Coverage Δ% Δ Uncovered
projects/packages/forms/src/class-jetpack-forms.php 4/15 (26.67%) -6.67% 1 ❤️‍🩹
projects/packages/forms/src/contact-form/class-contact-form-endpoint.php 579/652 (88.80%) -0.07% 0 💚
projects/packages/forms/src/contact-form/class-contact-form-plugin.php 424/1305 (32.49%) 0.02% -1 💚
projects/packages/forms/src/util/get-preferred-responses-view.js 0/2 (0.00%) 0.00% -1 💚
projects/packages/forms/src/blocks/contact-form/class-contact-form-block.php 395/591 (66.84%) 0.34% -3 💚

Full summary · PHP report · JS report

Coverage check overridden by Coverage tests to be added later Use to ignore the Code coverage requirement check when tests will be added in a follow-up PR .

@CGastrell CGastrell requested a review from a team September 23, 2025 21:46
@CGastrell CGastrell force-pushed the remove/forms-dashboard-switch-class branch from 9123262 to 0e9a2ce Compare September 24, 2025 04:41
@github-actions github-actions bot added the Docs label Sep 24, 2025
$footer_mark_as_spam_url = '';
if ( $feedback_status !== 'jp-temp-feedback' ) {
$dashboard_url = ( new Dashboard_View_Switch() )->get_forms_admin_url( $status, true ) . '&r=' . $post_id;
$dashboard_url = Forms_Dashboard::get_forms_admin_url( $status ) . '&r=' . $post_id;
Copy link
Contributor

Choose a reason for hiding this comment

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

Nitpick: $status is a confusing name, $tab would work better.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I'll agree with you semantically, but as the tab also represents the post status, I think it can stay. Besides, it's unrelated to the main goal of this PR.

Copy link
Contributor

@vianasw vianasw left a comment

Choose a reason for hiding this comment

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

I've added a few comments that aren't blockers, but there are e2e tests failing that need fixing. I've manually tested it and everything seemed to be working fine.

@CGastrell CGastrell requested a review from vianasw September 24, 2025 12:47
@CGastrell CGastrell merged commit 8d468b3 into trunk Sep 24, 2025
77 of 83 checks passed
@CGastrell CGastrell deleted the remove/forms-dashboard-switch-class branch September 24, 2025 13:45
@github-actions github-actions bot added this to the jetpack/15.1 milestone Sep 24, 2025
@github-actions github-actions bot removed the [Status] Needs Review This PR is ready for review. label Sep 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

[Block] Contact Form Form block (also see Contact Form label) Coverage tests to be added later Use to ignore the Code coverage requirement check when tests will be added in a follow-up PR Docs [Feature] Contact Form [Package] Forms [Plugin] Jetpack Issues about the Jetpack plugin. https://wordpress.org/plugins/jetpack/ [Tests] Includes Tests [Type] Janitorial

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants