Skip to content

feat(product): formalize product data contract and decouple from assessments#23359

Draft
FAMarfuaty wants to merge 4 commits into
634-api-migration-define-a-serializable-paperkeyphrase-input-contract-for-non-wordpress-consumersfrom
657-api-migration-formalize-the-product-customdata-contract-and-decouple-producttype-from-the-e-commerce-assessments
Draft

feat(product): formalize product data contract and decouple from assessments#23359
FAMarfuaty wants to merge 4 commits into
634-api-migration-define-a-serializable-paperkeyphrase-input-contract-for-non-wordpress-consumersfrom
657-api-migration-formalize-the-product-customdata-contract-and-decouple-producttype-from-the-e-commerce-assessments

Conversation

@FAMarfuaty

Copy link
Copy Markdown
Contributor

Context

Summary

This PR can be summarized in the following changelog entry:

Relevant technical choices:

Test instructions

Test instructions for the acceptance test before the PR gets merged

This PR can be acceptance tested by following these steps:

Relevant test scenarios

  • Changes should be tested with the browser console open
  • Changes should be tested on different posts/pages/taxonomies/custom post types/custom taxonomies
  • Changes should be tested on different editors (Default Block/Gutenberg/Classic/Elementor/other)
  • Changes should be tested on different browsers
  • Changes should be tested on multisite

Test instructions for QA when the code is in the RC

  • QA should use the same steps as above.

QA can test this PR by following these steps:

Impact check

This PR affects the following parts of the plugin, which may require extra testing:

Other environments

  • This PR also affects Shopify. I have added a changelog entry starting with [shopify-seo], added test instructions for Shopify and attached the Shopify label to this PR.
  • This PR also affects Yoast SEO for Google Docs. I have added a changelog entry starting with [yoast-doc-extension], added test instructions for Yoast SEO for Google Docs and attached the Google Docs Add-on label to this PR.

Documentation

  • I have written documentation for this change. For example, comments in the Relevant technical choices, comments in the code, documentation on Confluence / shared Google Drive / Yoast developer portal, or other.

Quality assurance

  • I have tested this code to the best of my abilities.
  • During testing, I had activated all plugins that Yoast SEO provides integrations for.
  • I have added unit tests to verify the code works as intended.
  • If any part of the code is behind a feature flag, my test instructions also cover cases where the feature flag is switched off.
  • I have written this PR in accordance with my team's definition of done.
  • I have checked that the base branch is correctly set.
  • I have run grunt build:images and committed the results, if my PR introduces or edits images or SVGs.

Innovation

  • No innovation project is applicable for this PR.
  • This PR falls under an innovation project. I have attached the innovation label.
  • I have added my hours to the WBSO document.

Fixes #

@FAMarfuaty FAMarfuaty force-pushed the 657-api-migration-formalize-the-product-customdata-contract-and-decouple-producttype-from-the-e-commerce-assessments branch from 579fc01 to db542ef Compare June 15, 2026 14:09
@FAMarfuaty FAMarfuaty changed the base branch from trunk to 634-api-migration-define-a-serializable-paperkeyphrase-input-contract-for-non-wordpress-consumers June 15, 2026 14:09
@github-actions

Copy link
Copy Markdown

A merge conflict has been detected for the proposed code changes in this PR. Please resolve the conflict by either rebasing the PR or merging in changes from the base branch.

…input-contract-for-non-wordpress-consumers' of github.com:Yoast/wordpress-seo into 657-api-migration-formalize-the-product-customdata-contract-and-decouple-producttype-from-the-e-commerce-assessments
Adds a typed, validated productData field to the PaperDTO input contract (productData.js / productDataSchema), wired through toPaper onto Paper.productData. The narrower that applies it at the consumption boundary, normalizeProductData, lives in a separate zod-free module that the assessments import directly, keeping zod out of the core analysis bundle.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@FAMarfuaty FAMarfuaty force-pushed the 657-api-migration-formalize-the-product-customdata-contract-and-decouple-producttype-from-the-e-commerce-assessments branch from d3001bc to 7c3c7f6 Compare June 16, 2026 06:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant