From fb0ac826df8785435190a31a6225994382d61037 Mon Sep 17 00:00:00 2001 From: Wolfgang Thomas Date: Mon, 24 Oct 2022 14:44:18 +0200 Subject: [PATCH] Fix potentially confusing regex example. The regex only matches files ending in .jpg, so the example should reflect this. --- content/md/assets/about-product-link-rules.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/md/assets/about-product-link-rules.md b/content/md/assets/about-product-link-rules.md index 749a8f1d21e..15a26501b39 100644 --- a/content/md/assets/about-product-link-rules.md +++ b/content/md/assets/about-product-link-rules.md @@ -125,7 +125,7 @@ The regexp above will split the source string into two parts, thanks to two name - `(?.*)` is the first capture group. It is named `product_ref`. So, the result of this capture will be sent into the `product_ref` asset attribute. The `product_ref` attribute should exist in the asset family. - `(?.*)` is the second capture group. It is named `attribute_ref`. So, the result of this capture will be sent to the `attribute_ref` asset attribute. The `attribute_ref` attribute should exist in the asset family. -Let's say our source string is equal to `Victor_packshot.png`. After the naming convention application, the `product_ref` asset attribute will contain the value "Victor" and the `attribute_ref` asset attribute will contain the value "packshot". +Let's say our source string is equal to `Victor_packshot.jpg`. After the naming convention application, the `product_ref` asset attribute will contain the value "Victor" and the `attribute_ref` asset attribute will contain the value "packshot". #### Abortion on error