Deutsche Version

Back to overview

Cart & Checkout Attributes: Technical

Decision flow

graph TD
    A["Order item in cart/checkout/summary"] --> B{"Kill switch active?"}
    B -->|No| C["Nothing rendered"]
    B -->|Yes| D{"Does the order item have a value?"}
    D -->|No| C
    D -->|Yes| E{"Display config exists?"}
    E -->|No| C
    E -->|Yes| F{"visibleInCart / checkoutVisibility set?"}
    F -->|No| C
    F -->|Yes| G["Render via SyliusAttribute partial"]

Plugin structure

src/
  Entity/                  ProductAttributeDisplayConfig, Settings/CartCheckoutAttributesSettings
  Enum/                    CheckoutVisibility
  Api/                     State providers for both API resources
  Form/                    Type and extension class for the admin form
  Command/                 SetupCommand
  Controller/Admin/        CartCheckoutAttributesSettingsController
  Menu/                    AdminMenuListener, MenuGroup
  Migrations/              3 Doctrine migrations
  Twig/                    CartCheckoutAttributeValuesExtension
config/
  routes/                  admin.yaml (required import), shop.yaml (empty, API comes via API Platform)
  twig_hooks/               admin.yaml, shop.yaml
  services.php
templates/
  admin/product_attribute/form/
  shop/cart/, shop/checkout/, shop/shared/order/

Entities & migrations

All three migrations are plain MySQL DDL and skip themselves on any other database.

CheckoutVisibility enum

enum CheckoutVisibility: string
{
    case NotVisible = 'not_visible';
    case Visible = 'visible';
    case Mandatory = 'mandatory';
}

By this construction, Mandatory is always checkout-visible - there is no combination that could mean "mandatory but hidden". visibleInCart is its own, independent boolean field.