Uploaded image for project: 'Camunda Optimize'
  1. Camunda Optimize
  2. OPT-7364

Abstract MultiValueInput common logic to separate component

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Unresolved
    • Icon: L3 - Default L3 - Default
    • None
    • None
    • frontend
    • None
    • Not defined

      Context:

      During the carbonisation of Optimize we used our custom 
      MultiValueInput component from c4 library. This component is just a barebone UI element without any control logic and this led to some code duplication in for example MultiEmailInput and FilterInstance components.
       
      AT:
      Create custom component to abstract the common logic and reduce the code duplication.

        This is the controller panel for Smart Panels app

            [OPT-7364] Abstract MultiValueInput common logic to separate component

            Michal Konopski created issue -
            Michal Konopski made changes -
            Status Original: Triage [ 10612 ] New: Ready [ 10005 ]
            Michal Konopski made changes -
            Status Original: Ready [ 10005 ] New: In Development [ 10312 ]
            Michal Konopski made changes -
            Status Original: In Development [ 10312 ] New: Ready [ 10005 ]

            Omran Abazeed added a comment -

            This ticket was migrated to github: https://github.com/camunda/camunda-optimize/issues/10043. Please use this link for any future references and continue any discussion there.

            Omran Abazeed added a comment - This ticket was migrated to github: https://github.com/camunda/camunda-optimize/issues/10043 . Please use this link for any future references and continue any discussion there.

              Unassigned Unassigned
              michal.konopski Michal Konopski
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: