Page Comparison

• Create the Fee Restaurant Config fields

  • path: intl-whitelabel-cms/schemas/fees/documents/fee-restaurant-config.tsx

  • path: intl-whitelabel-cms/schemas/fees/documents/fee-restaurant-config-list.tsx

  • Using the method bases create;

    • See the acceptance criteria: Sanity > Fee Restaurant Config

    • http://localhost:3333/desk/orderLevelContent;loyalty;loyaltyConfigs;featureLoyaltyUi

    • http://localhost:3333/desk/marketingContent;features;featureMenu

• After the first publish we will need to disable the fields:

  • Default Config

    

  • Fee Type

    

As the Fee Config document is used in the Fee Restaurant Config document the user can change the toggle even if the document is already published. As we don’t find a way to control this we need to ensure that the user will not be able to change the value of the toggle after the first publish.

Sanity doc:

https://dev-plk-es-whitelabel-cms.rbi.tools/desk/marketingContent;features;featureFee;feesConfig

To achieve that, we can:

1. Create a custom publish action (https://www.sanity.io/docs/document-actions)

   1. This action will be responsible for setting true on the new custom field isPublished (see below for more details) - https://www.sanity.io/docs/document-actions#362c883e4421 and https://www.sanity.io/docs/http-patches#6TPENSW3

2. Condition this new action to be only available for the Fee Config document (without affecting the other documents)

3. Create a new custom field in the Fee Config option to know if the document is already published or not (the name can be isPublished, for example)

   1. Add the hidden to this new field, as the user doesn’t need to see it. This field will only be used to control if the toggle is read-only or not (aka disabled)

4. Add the readOnly property to the Default Config toggle using the new isPublished prop

Demonstration

• Create a new Fragment and change the RestaurantGroup queries

  Image Removed

  query to get the Sanity values;

• Run apollo generate to create the sanity graphql method;

• Create a feature flag to use the new fields or validation (if using the existing hook);Create a method to validate the fee values described in the Whitelabel Acceptance Criteria:

• Add the Fee discount message on the table fee modal

  • The message needs to use the method created to validate he the fee values