Integration + Product + Category #17
Conversation
|
| currencyCode | ||
| } | ||
| featuredAsset { | ||
| source |
There was a problem hiding this comment.
use the preview property any time you get an Asset - the source is the source binary and might be very large, whereas preview is constrained to a sensible file size.
| slug | ||
| featuredAsset { | ||
| id | ||
| name |
There was a problem hiding this comment.
If you need to actually display the collection image, get the preview property.
| filters { | ||
| code | ||
| } | ||
| translations { |
There was a problem hiding this comment.
Normally you don't need to fetch the translations field, as the correct translated values (name, slug, description) are automatically populated into the Collection type at runtime by Vendure, based on the current context (i.e. the current channel's default language, or the current language as specified by the languageCode query param.
| slug | ||
| description | ||
| } | ||
| productVariants { |
There was a problem hiding this comment.
If the intention is to list all the variants in a collection, I recommend using the search query with the corresponding collectionId or collectionSlug input argument. This is a much more efficient way to get that data.
|
Currently added category page. The only thing left is to implement remaining getters. We have a category page listing products that also have correct links to product page. Unfortunately I faced a problem with displaying product prices on category page when using search query with groupByProduct option. It does not return any price. I asked Michael for the possible sollutions to that problem. |
|
Displaying sorting options and filters |
|
Also, fixed problem with displaying prices in search query thanks to @michaelbromley |
|
Category page is now working correctly. |
Baroshem
changed the title
| push: | ||
| branches: | ||
| - main | ||
| - develop |
There was a problem hiding this comment.
AFAIK you have only main branch so this is unnecessary
| - develop |
| pull_request: | ||
| branches: | ||
| - main | ||
| - develop |
There was a problem hiding this comment.
same as above
| - develop |
| } | ||
|
|
||
| const getProduct = async (context: Context, params: ProductParams, customQuery?: CustomQuery): Promise<ApolloQueryResult<ProductData>> => { |
There was a problem hiding this comment.
IMO better returning type will be Promise<ProductData>
| ); | ||
|
|
||
| try { | ||
| const request = await (context.client as ApolloClient<any>).query<ProductData>({ |
There was a problem hiding this comment.
to achieve the above over here you need to destructor request.
| product?.images[0] || | ||
| "https://s3-eu-west-1.amazonaws.com/commercetools-maximilian/products/081223_1_large.jpg"; | ||
| function getItemImage(item: CartItem): string { | ||
| return 'https://s3-eu-west-1.amazonaws.com/commercetools-maximilian/products/081223_1_large.jpg'; |
There was a problem hiding this comment.
add todo cuz now is hardcodeded
Closes #16
Closes #1
Closes #3
Closes #4
Closes #5
Closes #2
I have created a connection between local Vendure server created with a command
npx @vendure/create my-appand developed basic getCategory functionality and full getProduct functionality. This is Work in Progress Pull Request because I have to finish getCategory functionality, write unit tests and add docs. I also updated the repo to the latest boilerplate state (that's why there is so many changes).Product Page
Product details
