Improve type safety for SEO data utilities #763
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
WHY are these changes introduced?
This PR brings more consistency to the typing of the seo data utilities. This preserves internal consistency within the module and will hopefully help folks in userland who bring the seo data utility module into their own repos.
WHAT is this pull request doing?
Previously, the
collection
andproduct
seo data utilities in the demo store inferred the types of the data they returned. In contrast, other seo data utililties annotated the return type with theSeoConfig
generic.I realized that the
product
andcollection
utilities were using extracted functions for creating thejsonLd
values, but those functions returned the incorrect type. I removed the unnecessary array typing and was then able to add the return typing tocollection
andproduct
.Continuation of #757
Checklist