Open dalyathan opened 1 month ago
The changes in this pull request include the addition of a new GraphQL query, getKlaviyoReviews
, in the Vendure Klaviyo plugin, which allows users to fetch all reviews from Klaviyo. This update is documented in the changelog and README. New types and a resolver class for handling the query have been introduced, along with a service method to interact with the Klaviyo API. Additionally, test cases and mock data have been added to ensure functionality.
File Path | Change Summary |
---|---|
packages/vendure-plugin-klaviyo/CHANGELOG.md | Updated changelog for version 1.3.0, added entry for getKlaviyoReviews . |
packages/vendure-plugin-klaviyo/README.md | Added documentation for fetching reviews with a GraphQL query example. |
packages/vendure-plugin-klaviyo/src/api/api-extensions.ts | Introduced KlaviyoReviewStatus enum, new types, and getKlaviyoReviews query. |
packages/vendure-plugin-klaviyo/src/api/klaviyo-shop.resolver.ts | Added KlaviyoShopResolver class and getKlaviyoReviews method. |
packages/vendure-plugin-klaviyo/src/klaviyo.plugin.ts | Updated KlaviyoPlugin to include KlaviyoShopResolver and shopApiExtension . |
packages/vendure-plugin-klaviyo/src/klaviyo.service.ts | Added getAllReviews method to retrieve reviews from Klaviyo API. |
packages/vendure-plugin-klaviyo/test/e2e.spec.ts | Added test case for fetching all reviews from Klaviyo. |
packages/vendure-plugin-klaviyo/test/mock-data.ts | Introduced mock-data.ts with klaviyoReviews constant. |
packages/vendure-plugin-klaviyo/test/queries.ts | Added getAllKlaviyoReviews GraphQL query. |
Objective | Addressed | Explanation |
---|---|---|
Implement getKlaviyoReviews() query in Klaviyo plugin (#516) |
✅ |
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?
Placed on hold for now, because of a change in priority in the client project
Description
The changes in this PR implement and close #516
Deploy
This needs to happen to deploy this feature, for example:
Breaking changes
Does this PR include any breaking changes we should be aware of? NO
Screenshots
Checklist
📌 Always:
👍 Most of the time:
📦 For publishable packages:
package.json
CHANGELOG.md
See this example