Help Center: extend post fetch endpoint

[arcangelini]

Proposed changes:

Adds the post_url arg to help-center/fetch-post endpoint.

This is part of a larger task to allow support guide links in Help Center open within Help Center.
PR for the main package ⇢ Automattic/wp-calypso#92745
PR for the main endpoint ⇢ D155970-code

Other information:

• 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)?

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

Nope

Testing instructions:

This does not add any feature to test so really we are only testing to make sure the endpoint works and that Help Center does not break.

1. Open the dev console in your browser.
2. Open the Help Center and open a support guide.
3. Search for a guide and open that as well.
4. Go to the Network tab in your dev console and view the request for /fetch-post
5. Copy this request as a fetch
6. Paste this in the console and replace post_id and blog_id with post_url and the url of an article.
7. All requests should return 200 with the correct article.

fetch("https://busineselini.wpcomstaging.com/wp-json/help-center/fetch-post?post_id=158974&blog_id=9619154&_locale=user", {
"headers": ...
  });

fetch("https://busineselini.wpcomstaging.com/wp-json/help-center/fetch-post?post_url=https://en.support.wordpress.com/getting-started-with-wordpress-com/&_locale=user", {
  "headers": ...
  });

[github-actions]

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 WordPress.com Simple 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, and enable the update/help-center-post-enpoint branch.

  • For jetpack-mu-wpcom changes, also add define( 'JETPACK_MU_WPCOM_LOAD_VIA_BETA_PLUGIN', true ); to your wp-config.php file.

• To test on Simple, run the following command on your sandbox:

  bin/jetpack-downloader test jetpack-mu-wpcom-plugin update/help-center-post-enpoint
  

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]

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 Team Review, ...).
  
• ✅ 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 🤖

---

The e2e test report can be found here. Please note that it can take a few minutes after the e2e tests checks are complete for the report to be available.

---

Once your PR is ready for review, check one last time that all required checks appearing at the bottom of this PR are passing or skipped.
Then, add the "[Status] Needs Team Review" label and ask someone from your team review the code. Once reviewed, it can then be merged.
If you need an extra review from someone familiar with the codebase, you can update the labels from "[Status] Needs Team Review" to "[Status] Needs Review", and in that case Jetpack Approvers will do a final review of your PR.

[arcangelini]

I tested this in Simple and Atomic environments and everything seems to be A-OK.

[escapemanuele]

This reflects the changes made to the endpoint 👍

[agrullon95]

Tested on atomic site and was able to retrieve the article related info via post_url + blog_id and post_url.