Replies: 2 comments 4 replies
-
i'm all for option 3 :) (merch-modal instead of commerce-modal), i'd say in overall debate centralisation vs duplication, where risk is to propagate problems in one click in case of centralisation, that if we do our testing job right (and it's easier to do so with less code), we should not be concerned. to take one step in advance to @yesil, we could have commerce-modal and commerce-card-modal as CRM has no card, but i'm sure we could keep things simple |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
With TWP modal being in active development (see test content and modal in action) we need to decide on block namings.
At the moment we have 3 types of modals. TWP, D2P and CRM (content rich modal). TWP and D2P modals have no structural differences and their content structure most likely be the same. CRM content is different.
Option 1
to have a separate block for each:
pros: content authors and dev's can immediately understand what kind of modal it is
cons: either code duplication between twp and d2p blocks, or, if we have a common file, we will need to load 2 js files instead of one.
Option 2
Option 3
with variations 'twp', 'd2p', 'crm'
cons: higher impact in case the bug is introduced in the common block. bigger scope of validation on each change to block.
Please feel free to suggest more options.
Beta Was this translation helpful? Give feedback.
All reactions