Uh oh!
There was an error while loading. Please reload this page.
Personalized products - #39
Conversation
Deploying with |
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs | developer-docs | 220696a | Commit Preview URL Branch Preview URL | Jul 31 2026, 08:59 AM |
| /// <reference types="next" /> | ||
| /// <reference types="next/image-types/global" /> | ||
| import"./.next/dev/types/routes.d.ts"; | ||
| import"./.next/types/routes.d.ts"; |
There was a problem hiding this comment.
WARNING:next-env.d.ts is auto-generated by Next.js; manual edits are overwritten on the next next dev/next build. The comment in this file explicitly says it should not be edited.
If this change is required to fix a TypeScript build, do it upstream in Next.js rather than committing it here. If it's just a drift correction that Next will regenerate, drop it from this PR to avoid future rebase churn.
Reply with @kilocode-bot fix it to have Kilo Code address this issue.
| | request | The current `request` context object. | | ||
| | product | The `product` context object. | | ||
| | form_type | The form type, typically `'single'`. | | ||
| | quantity_type | Accepts `'single'` or `'multiple'`. | |
There was a problem hiding this comment.
WARNING: The third positional argument to {% cart_form %} was renamed from form_type to quantity_type in this table, but I see no other change in the PR that proves the underlying tag keyword was also renamed. If the platform code still accepts form_type, this table is now incorrect and will mislead theme authors.
Verify against the source of the cart_form template tag and either keep the documented name (form_type) or rename the tag keyword in the same change so the docs stay accurate.
Reply with @kilocode-bot fix it to have Kilo Code address this issue.
| {% purchase_info_for_product request product as session %} | ||
| {% if session.availability.is_available_to_buy %} | ||
| {% cart_form request product 'single' as cart_form %} | ||
| <form id="add-to-cart" class="row g-3" action="{% url 'cart:add' pk=product.pk %}" method="post"> |
There was a problem hiding this comment.
WARNING: The form action now uses {% url 'cart:add' pk=product.pk %} here, but the cart_form invocation snippet immediately above on line 100 (which this PR did not touch) still uses {% url 'cart:add' product.slug %}. Two different URL kwargs on the same docs page will confuse readers.
Pick one (PK or slug) and make both examples use it, or call out explicitly when the add endpoint expects pk versus slug.
Reply with @kilocode-bot fix it to have Kilo Code address this issue.
| {% purchase_info_for_product request product as session %} | ||
| {% if session.availability.is_available_to_buy %} | ||
| {% cart_form request product 'single' as cart_form %} | ||
| <form id="add-to-cart" action="{% url 'cart:add' pk=product.pk %}" method="post"> |
There was a problem hiding this comment.
WARNING: Same URL-kwargs inconsistency surfaces again: this guide uses {% url 'cart:add' pk=product.pk %} while the cart_form tag reference still uses product.slug on tags.mdx:100. Make the two pages agree.
Reply with @kilocode-bot fix it to have Kilo Code address this issue.
| | Empty values | A property submitted with an empty value does not create a separate line. It is still recorded on the line, so guard your display with `{% if property.value %}`. | | ||
| | Hidden properties | Property names starting with an underscore, such as `properties[_source]`, are stored but excluded from `line.properties` and from the Storefront GraphQL API. Use them for data that should not be shown to customers. | | ||
| | Value length | Values longer than 500 characters are truncated to 500 characters. | | ||
| | Checkboxes | When a checkbox named `properties[...]` changes, the value submitted is `yes` or `no`. | |
There was a problem hiding this comment.
SUGGESTION: The "Checkboxes" row promises that a checkbox named properties[...] submits yes or no, but no example input is shown anywhere in the guide. Add a short <input type="checkbox" name="properties[GiftWrap]"> example alongside the existing text input so theme authors do not have to guess the wire format.
Reply with @kilocode-bot fix it to have Kilo Code address this issue.
| | Template | View-Specific Context | | ||
| | ----- | ------ | | ||
| | `templates/index.html` | Global objects only. Use the [`where`](/docs/storefront/themes/templates/tags#where) tag to query products and categories. | | ||
| | `templates/cart.html` | `formset` (cart line forms, each `form.instance` is a [line](#line)) | |
There was a problem hiding this comment.
SUGGESTION: The added templates/cart.html row says the context provides formset, but the formset type/shape is documented only via the new ### line section above. Consider giving formset its own short entry (or at minimum a sentence under line) so readers understand they get a Django formset of line forms, not a plain list.
Reply with @kilocode-bot fix it to have Kilo Code address this issue.
Code Review SummaryStatus: No New Issues Found | Recommendation: Address existing findings before merge Overview
The incremental commit (220696a) only changes one line in the auto-generated Files Reviewed (1 file in incremental diff)
Fix these issues in Kilo Cloud Previous Review Summary (commit dda098b)Current summary above is authoritative. Previous snapshots are kept for context only. Previous review (commit dda098b)Status: 6 Issues Found | Recommendation: Address before merge Overview
Issue Details (click to expand)WARNING
SUGGESTION
Files Reviewed (5 files)
Reviewed by minimax-m3 · Input: 23.8K · Output: 1.7K · Cached: 143.8K |
Uh oh!
There was an error while loading. Please reload this page.
No description provided.