Implement shopper products

[alexvuong]

Description

This PR implemented useShopperCategories, useShopperCategory,useShopperProduct, useShopperProduct

Types of Changes

• Bug fix (non-breaking change that fixes an issue)
• New feature (non-breaking change that adds functionality)
• Documentation update
• Breaking change (could cause existing functionality to not work as expected)
• Other changes (non-breaking changes that does not fit any of the above)

Breaking changes include:

• Removing a public function or component or prop
• Adding a required argument to a function
• Changing the data type of a function parameter or return value
• Adding a new peer dependency to package.json

Changes

How to Test-Drive This PR

• Pull the code
• npm ci
• cd to the test project, npm start
• Before clicking on any links, please grab a token in your console and put it inside your Provider here
• Reload and see no error in the console, which means you are logged in as guest
• Navigate around to see the hooks in actions!

Checklists

General

• Changes are covered by test cases
• CHANGELOG.md updated with a short description of changes (not required for documentation updates)

Accessibility Compliance

You must check off all items in one of the follow two lists:

• There are no changes to UI

or...

• Changes were tested with a Screen Reader (iOS VoiceOver or Android Talkback) and had no issues
• Changes comply with WCAG 2.0 guidelines levels A and AA
• Changes to common UI patterns and interactions comply with WAI-ARIA best practices

Localization

• Changes include a UI text update in the Retail React App (which requires translation)

[vmarta]

If you're curious why the CI tests are failing, it's because we need to import regenerator-runtime package when testing async functions.

I saw it in my branch, and I fixed it by reusing the jest setup file from internal-lib-build. That file has imported the regenerator-runtime package:

pwa-kit/packages/internal-lib-build/configs/jest/setup-jest.js

Line 10 in c3b6c84

import 'regenerator-runtime/runtime'

Hopefully I can merge my PR soon, so you can pull it into your branch.

[vmarta]

Other than this 1 comment, the whole PR looks good to me. Feel free to ask for someone else's feedback too, in case I overlook something.

[kevinxh]

what happens if you don't add this if statement?

Will commerce-sdk-isomorphic throw a similar error? Should we use that error? Because ultimately the schema is coming from the commerce-sdk-isomorphic parameters

[alexvuong]

If we don't catch the error here, it will hit the network and returns an error, since we are using react-query, by default it will retry 3 times before returning the error. I'd it is best if we can catch the error here before it hits the network. Here is what looks like if we don't catch that ids first

[kevinxh]

I don't think we need this esModuleInterop flag? right?

[alexvuong]

we need that to be true to avoid the complain from Typescript. By default, it is set to false

[kevinxh]

left some non-blocking comments.

We had a discussion today and we noticed the internal-lib-build build script is not working correctly, the typescript declaration files are not generated in published package. We agree to fix that in a separate PR.