[TITAN - 280] - Produce mock data for product components and details pages #5
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
Adding stubs for a full list of products from Shopify and a single product from the storefront API. The latter is based on this POC where the product detail paged is composed of a mix of ACM model and Shopify data using the unified schema. It hasn't been created yet so is just a mock i.e
shopifySite {}To mock the product detail pages without the storefront API we can just write code that will search the stub for the product by
handle.As I was generating these mocks I made real requests in Shopify dashboard, the fragments we can use for these later are added as well. (The storefront API one is just a concept though as mentioned before it doesnt exist yet)