From f00ba28f64e4589f44160346dd11a207919b6a46 Mon Sep 17 00:00:00 2001 From: Pedro Antunes <47991446+PedroAntunesCosta@users.noreply.github.com> Date: Mon, 30 Mar 2026 17:11:46 -0300 Subject: [PATCH] docs: rename Trade Policy to Sales Channel and fix emoji shortcodes --- docs/README.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/docs/README.md b/docs/README.md index 6e9d4cc..ecc041b 100644 --- a/docs/README.md +++ b/docs/README.md @@ -1,6 +1,6 @@ 📢 Use this project, [contribute](https://github.com/vtex-apps/challenge-tp-condition) to it or open issues to help evolve it using [Store Discussion](https://github.com/vtex-apps/store-discussion). -# Challenge Trade Policy Condition +# Challenge sales channel condition [![All Contributors](https://img.shields.io/badge/all_contributors-0-orange.svg?style=flat-square)](#contributors-) @@ -8,7 +8,9 @@ Used in B2B environments, the Challenge block is a non-rendered block responsible for checking if a user is allowed to access the store's content. -:information_source: This check is made according to the Condition Rule specified in the Trade Policy configuration, one of the steps needed to [**configure a B2B environment in VTEX IO**](https://vtex.io/docs/recipes/store/configuring-a-b2b-environment). +ℹ️ This check is made according to the Condition Rule specified in the Sales Channel configuration, one of the steps needed to [**configure a B2B environment in VTEX IO**](https://vtex.io/docs/recipes/store/configuring-a-b2b-environment). + +> ⚠️ The feature formerly known as **Trade Policy** has been renamed to **Sales Channel**. Code references (e.g., `challenge.trade-policy-condition`) still use the old naming for backward compatibility. ## Configuration @@ -56,7 +58,7 @@ Used in B2B environments, the Challenge block is a non-rendered block responsibl | `forbiddenRedirectPath` | `string` | Path to which the logged in user will be redirected if not allowed access according to the Condition Rule | `/login` | | `defaultContentVisibility` | `enum` | Whether the store's content should be visible (`visible`) or hidden (`hidden`) while the Challenge block is verifying the user's access permission | `visible` | -:warning: Using `hidden` as the `defaultContentVisibility` value result in the entire page's content being rendered on the client side (in a scenario in which the check concludes that the user has permission to access the store). The page will not be Server Side Rendered (SSR) due to the fact that this verification process is user-based, making it impossible to cache. +> ⚠️ Using `hidden` as the `defaultContentVisibility` value result in the entire page's content being rendered on the client side (in a scenario in which the check concludes that the user has permission to access the store). The page will not be Server Side Rendered (SSR) due to the fact that this verification process is user-based, making it impossible to cache. ## Customization