{"id":123,"date":"2025-11-21T11:36:24","date_gmt":"2025-11-21T11:36:24","guid":{"rendered":"https:\/\/magendoo.ro\/insights\/?p=123"},"modified":"2025-11-21T11:36:24","modified_gmt":"2025-11-21T11:36:24","slug":"magento-2-on-php-8-5-having-fun-with-the-pipe-operator","status":"publish","type":"post","link":"https:\/\/magendoo.ro\/insights\/magento-2-on-php-8-5-having-fun-with-the-pipe-operator\/","title":{"rendered":"Magento 2 on PHP 8.5: Having Fun with the Pipe Operator"},"content":{"rendered":"\n

PHP 8.5 adds a tiny new syntax feature that fits Magento 2 code really<\/em> well: the pipe operator |><\/code>.<\/p>\n\n\n\n

It doesn\u2019t give you new superpowers, but it makes a ton of existing Magento patterns cleaner and easier to read\u2014especially anything that looks like \u201ctake this value, transform it, transform it again, transform it again\u2026\u201d.<\/p>\n\n\n\n

Let\u2019s walk through how Magento 2 code can look once you\u2019re on PHP 8.5 and start leaning into |><\/code>.<\/p>\n\n\n\n

\n\n\n\n

Quick recap: what |><\/code> actually does<\/h2>\n\n\n\n

The pipe operator lets you write this:<\/p>\n\n\n\n

$result = \" Hello World \"\n    |> trim(...)\n    |> strtoupper(...)\n    |> strrev(...);\n<\/code><\/pre>\n\n\n\n
instead of:<\/p>\n\n\n\n
$result = strrev(strtoupper(trim(\" Hello World \")));\n<\/code><\/pre>\n\n\n\n
or the classic temp-variable ladder:<\/p>\n\n\n\n
$str = \" Hello World \";\n$str = trim($str);\n$str = strtoupper($str);\n$result = strrev($str);\n<\/code><\/pre>\n\n\n\n
Rules of the game:<\/p>\n\n\n\n
    \n
  • The value on the left<\/strong> is passed as the first (and required) argument<\/strong> to whatever\u2019s on the right<\/strong>.<\/li>\n\n\n\n
  • The right side must be a callable<\/strong> that takes (at least) one argument:\n
      \n
    • trim(...)<\/code>, $this->doSomething(...)<\/code>, SomeClass::staticMethod(...)<\/code><\/li>\n\n\n\n
    • fn ($x) => ...<\/code><\/li>\n<\/ul>\n<\/li>\n\n\n\n
    • It evaluates left \u2192 right, line by line.<\/li>\n<\/ul>\n\n\n\n
      Once you see it as \u201ca nice way to chain transformations\u201d, it clicks.<\/p>\n\n\n\n
      \n\n\n\n
      1. Collections & view models<\/h2>\n\n\n\n
      Magento loves collections and data massaging. That\u2019s a perfect fit for |><\/code>.<\/p>\n\n\n\n
      Before:<\/strong><\/p>\n\n\n\n
      $collection = $this->productCollectionFactory->create();\n$collection->addAttributeToSelect('*');\n$collection->addMinimalPrice()\n           ->addFinalPrice();\n\n$items = $collection->getItems();\n\n$items = array_filter($items, fn(Product $p) => $p->isSaleable());\n$items = array_map([$this, 'mapProductToDto'], $items);\n$items = $this->sortProductsByPrice($items);\n<\/code><\/pre>\n\n\n\n
      After, with pipe-friendly helpers:<\/strong><\/p>\n\n\n\n
      $products = $this->productCollectionFactory->create()\n    |> $this->loadProductCollection(...)\n    |> $this->filterSaleableProducts(...)\n    |> $this->mapProductsToDto(...)\n    |> $this->sortProductsByPrice(...);\n<\/code><\/pre>\n\n\n\n
      And the helpers:<\/p>\n\n\n\n
      private function loadProductCollection(\n    \\Magento\\Catalog\\Model\\ResourceModel\\Product\\Collection $collection\n): array {\n    $collection->addAttributeToSelect('*')\n               ->addMinimalPrice()\n               ->addFinalPrice();\n\n    return $collection->getItems();\n}\n\nprivate function filterSaleableProducts(array $products): array\n{\n    return array_filter(\n        $products,\n        static fn(\\Magento\\Catalog\\Model\\Product $p) => $p->isSaleable()\n    );\n}\n<\/code><\/pre>\n\n\n\n
      Each step does one thing, takes one argument, returns something. The pipe line at the top is basically the \u201cstory\u201d of how your data flows.<\/p>\n\n\n\n
      \n\n\n\n
      2. Request parameter cleanup<\/h2>\n\n\n\n
      Controllers and ViewModels always normalize request params. The pipe operator makes those little \u201csanitize\u201d sequences easier to scan.<\/p>\n\n\n\n
      Before:<\/strong><\/p>\n\n\n\n
      $page = (int) $this->getRequest()->getParam('p', 1);\n$page = max($page, 1);\n$page = min($page, self::MAX_PAGE);\n<\/code><\/pre>\n\n\n\n
      After:<\/strong><\/p>\n\n\n\n
      $page = $this->getRequest()->getParam('p', 1)\n    |> 'intval'\n    |> fn (int $p) => max($p, 1)\n    |> fn (int $p) => min($p, self::MAX_PAGE);\n<\/code><\/pre>\n\n\n\n
      Wrap the pattern once and reuse it:<\/p>\n\n\n\n
      private function sanitizeIntParam(string $name, int $default, int $min, int $max): int\n{\n    return $this->getRequest()->getParam($name, $default)\n        |> 'intval'\n        |> fn (int $v) => max($min, $v)\n        |> fn (int $v) => min($max, $v);\n}\n\n\/\/ Usage\n$page = $this->sanitizeIntParam('p', 1, 1, self::MAX_PAGE);\n<\/code><\/pre>\n\n\n\n
      \n\n\n\n
      3. Config pipelines<\/h2>\n\n\n\n
      Config values almost always need a bunch of cleanup: cast, trim, explode, filter.<\/p>\n\n\n\n
      Before:<\/strong><\/p>\n\n\n\n
      $value = $this->scopeConfig->getValue(\n    'vendor_module\/feature\/allowed_ids',\n    \\Magento\\Store\\Model\\ScopeInterface::SCOPE_STORE\n);\n\n$value = (string) $value;\n$value = trim($value);\n$value = strtolower($value);\n$ids   = array_filter(explode(',', $value));\n<\/code><\/pre>\n\n\n\n
      After:<\/strong><\/p>\n\n\n\n
      $ids = $this->scopeConfig\n    ->getValue('vendor_module\/feature\/allowed_ids', \\Magento\\Store\\Model\\ScopeInterface::SCOPE_STORE)\n    |> 'strval'\n    |> 'trim'\n    |> 'strtolower'\n    |> fn (string $v) => explode(',', $v)\n    |> 'array_filter';\n<\/code><\/pre>\n\n\n\n
      You read that top-to-bottom and instantly see what\u2019s going on.<\/p>\n\n\n\n
      \n\n\n\n
      4. Service workflows<\/h2>\n\n\n\n
      Application services (e.g. cart updates, order processing) are basically \u201cdo X, then Y, then Z\u201d pipelines already.<\/p>\n\n\n\n
      Before:<\/strong><\/p>\n\n\n\n
      $cart = $this->cartRepository->get($cartId);\n\n$cart = $this->discountApplier->apply($cart, $discountCode);\n$cart = $this->shippingEstimator->estimate($cart);\n$cart = $this->taxCalculator->calculate($cart);\n$cart = $this->totalsCollector->collect($cart);\n\n$this->cartRepository->save($cart);\n<\/code><\/pre>\n\n\n\n
      After:<\/strong><\/p>\n\n\n\n
      $cart = $this->cartRepository->get($cartId)\n    |> fn ($cart) => $this->discountApplier->apply($cart, $discountCode)\n    |> $this->shippingEstimator->estimate(...)\n    |> $this->taxCalculator->calculate(...)\n    |> $this->totalsCollector->collect(...);\n\n$this->cartRepository->save($cart);\n<\/code><\/pre>\n\n\n\n
      Or, if you\u2019re in the mood, including the save as the final step:<\/p>\n\n\n\n
      $this->cartRepository->get($cartId)\n    |> fn ($cart) => $this->discountApplier->apply($cart, $discountCode)\n    |> $this->shippingEstimator->estimate(...)\n    |> $this->taxCalculator->calculate(...)\n    |> $this->totalsCollector->collect(...)\n    |> fn ($cart) => $this->cartRepository->save($cart);\n<\/code><\/pre>\n\n\n\n
      That\u2019s a nice, linear description of the workflow.<\/p>\n\n\n\n
      \n\n\n\n
      5. Import \/ export & ETL-style code<\/h2>\n\n\n\n
      Importers and exporters scream \u201cpipeline\u201d: normalize \u2192 validate \u2192 enrich \u2192 persist.<\/p>\n\n\n\n
      $row\n    |> $this->normalizeRow(...)\n    |> $this->mapExternalToInternalSkus(...)\n    |> $this->validateRow(...)\n    |> $this->saveRow(...);\n<\/code><\/pre>\n\n\n\n
      Signatures stay simple:<\/p>\n\n\n\n
      private function normalizeRow(array $row): array;\nprivate function mapExternalToInternalSkus(array $row): array;\nprivate function validateRow(array $row): array;   \/\/ throws on errors\nprivate function saveRow(array $row): void;\n<\/code><\/pre>\n\n\n\n
      The last step returning void<\/code> is fine, since it\u2019s the end of the chain.<\/p>\n\n\n\n
      \n\n\n\n
      6. Plugins and observers<\/h2>\n\n\n\n
      After-plugins<\/h3>\n\n\n\n
      After-plugins usually adjust a result in a couple of steps. Perfect pipe territory.<\/p>\n\n\n\n
      public function afterGetPrice($subject, float $result): float\n{\n    return $result\n        |> fn (float $price) => $this->applyTierPrice($subject, $price)\n        |> fn (float $price) => $this->roundPrice($price)\n        |> fn (float $price) => $this->applyCustomerGroupAdjustment($subject, $price);\n}\n<\/code><\/pre>\n\n\n\n
      You instantly see the sequence of tweaks applied.<\/p>\n\n\n\n
      Observers<\/h3>\n\n\n\n
      Observers are often \u201cgrab event data, build a payload, send it somewhere\u201d.<\/p>\n\n\n\n
      public function execute(\\Magento\\Framework\\Event\\Observer $observer): void\n{\n    $order = $observer->getEvent()->getOrder();\n\n    $payload = $order\n        |> $this->orderToExportPayload(...)\n        |> $this->maskSensitiveData(...)\n        |> $this->serializePayload(...);\n\n    $this->queuePublisher->publish('order.export', $payload);\n}\n<\/code><\/pre>\n\n\n\n
      Again: straight line from source to sink.<\/p>\n\n\n\n
      \n\n\n\n
      7. Writing \u201cpipe-friendly\u201d Magento code<\/h2>\n\n\n\n
      The new operator pays off more if you nudge your APIs in its direction.<\/p>\n\n\n\n
      7.1 One main argument, return something<\/h3>\n\n\n\n
      Instead of designing methods like:<\/p>\n\n\n\n
      public function process(array &$data): void;\n<\/code><\/pre>\n\n\n\n
      prefer:<\/p>\n\n\n\n
      public function process(array $data): array;\n<\/code><\/pre>\n\n\n\n
      Same for domain classes: take one main value, return a new value (or the same object). That naturally fits into value |> method(...)<\/code>.<\/p>\n\n\n\n
      7.2 Tiny callable helpers<\/h3>\n\n\n\n
      A neat trick is to expose pipe-ready callables:<\/p>\n\n\n\n
      class DiscountApplier\n{\n    public function apply(string $code): callable\n    {\n        return fn (CartInterface $cart): CartInterface =>\n            $this->applyDiscount($cart, $code);\n    }\n\n    private function applyDiscount(CartInterface $cart, string $code): CartInterface\n    {\n        \/\/ ...\n    }\n}\n<\/code><\/pre>\n\n\n\n
      Now your workflow reads:<\/p>\n\n\n\n
      $cart = $cart\n    |> $this->discountApplier->apply($discountCode)\n    |> $this->taxCalculator->calculate(...)\n    |> $this->totalsCollector->collect(...);\n<\/code><\/pre>\n\n\n\n
      7.3 Invokable utilities<\/h3>\n\n\n\n
      Instead of static utility classes, small invokable services slot nicely into pipelines:<\/p>\n\n\n\n
      class FilterSaleableProducts\n{\n    public function __invoke(array $products): array\n    {\n        return array_filter(\n            $products,\n            static fn(\\Magento\\Catalog\\Model\\Product $p) => $p->isSaleable()\n        );\n    }\n}\n<\/code><\/pre>\n\n\n\n
      Used like:<\/p>\n\n\n\n
      $products = $collection->getItems()\n    |> $this->filterSaleableProducts(...)\n    |> $this->mapProductsToDto(...);\n<\/code><\/pre>\n\n\n\n
      \n\n\n\n
      8. When not<\/em> to use the pipe operator<\/h2>\n\n\n\n
      Don\u2019t force it everywhere. A few cases where plain old code is simpler:<\/p>\n\n\n\n
        \n
      • Heavy branching logic<\/strong> with lots of if<\/code>\/else<\/code> and early returns.<\/li>\n\n\n\n
      • Side-effect-heavy methods<\/strong> (sending emails, writing files, hitting multiple repositories) that don\u2019t really feel like \u201ctransform X into Y\u201d.<\/li>\n\n\n\n
      • Very long, twisty flows<\/strong> \u2013 if your pipe chain is 10+ steps and full of complex closures, breaking it into named methods is usually clearer.<\/li>\n<\/ul>\n\n\n\n
        As a rule of thumb: if you\u2019re transforming data and each step is small and focused, the pipe operator almost always improves readability. If you\u2019re orchestrating a multi-headed hydra of side effects, maybe keep that in a classic service method and use pipes only around the data shaping.<\/p>\n\n\n\n
        \n\n\n\n
        Wrap-up<\/h2>\n\n\n\n
        Once you\u2019re on PHP 8.5, the pipe operator gives Magento 2 code a nice little boost:<\/p>\n\n\n\n
          \n
        • Cleaner chains for collections, config values, and DTOs.<\/li>\n\n\n\n
        • More readable plugins, observers, and service workflows.<\/li>\n\n\n\n
        • A gentle push towards pure-ish, one-argument, testable functions.<\/li>\n<\/ul>\n\n\n\n
          You don\u2019t have to rewrite everything. Just start by:<\/p>\n\n\n\n
            \n
          • Extracting small transformation helpers,<\/li>\n\n\n\n
          • Making them take a single main argument and return a value,<\/li>\n\n\n\n
          • And then wiring them together with |><\/code> where it actually makes the code easier to follow.<\/li>\n<\/ul>\n\n\n\n
            If you want, you can drop in a real chunk of your Magento code and we can refactor it into a \u201cpipe-first\u201d version side by side.<\/p>\n","protected":false},"excerpt":{"rendered":"
            PHP 8.5 adds a tiny new syntax feature that fits Magento 2 code really well: the pipe operator |>. It doesn\u2019t give you new superpowers, but it makes a ton of existing Magento patterns cleaner and easier to read\u2014especially anything that looks like \u201ctake this value, transform it, transform it again, transform it again\u2026\u201d. Let\u2019s […]<\/p>\n","protected":false},"author":1,"featured_media":124,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"site-container-style":"default","site-container-layout":"default","site-sidebar-layout":"default","disable-article-header":"default","disable-site-header":"default","disable-site-footer":"default","disable-content-area-spacing":"default","footnotes":""},"categories":[9],"tags":[],"class_list":["post-123","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-magento-2"],"_links":{"self":[{"href":"https:\/\/magendoo.ro\/insights\/wp-json\/wp\/v2\/posts\/123","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/magendoo.ro\/insights\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/magendoo.ro\/insights\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/magendoo.ro\/insights\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/magendoo.ro\/insights\/wp-json\/wp\/v2\/comments?post=123"}],"version-history":[{"count":1,"href":"https:\/\/magendoo.ro\/insights\/wp-json\/wp\/v2\/posts\/123\/revisions"}],"predecessor-version":[{"id":125,"href":"https:\/\/magendoo.ro\/insights\/wp-json\/wp\/v2\/posts\/123\/revisions\/125"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/magendoo.ro\/insights\/wp-json\/wp\/v2\/media\/124"}],"wp:attachment":[{"href":"https:\/\/magendoo.ro\/insights\/wp-json\/wp\/v2\/media?parent=123"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/magendoo.ro\/insights\/wp-json\/wp\/v2\/categories?post=123"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/magendoo.ro\/insights\/wp-json\/wp\/v2\/tags?post=123"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}