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

Automatically identify dead code

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Unresolved
    • Icon: L3 - Default L3 - Default
    • None
    • None
    • frontend
    • M

      We have a linter plugin that produces warning if an import or variable is not used in a file or function. And we have a test that makes sure we use all the libraries we import.

      However, we have nothing that makes sure that the files we have in the repo are actually used anywhere. For example, on March 12 2018, we created an Async component file. One day later we decided that we want to solve the problem differently. However, we never deleted the then obsolete Async file. Until we noticed it more than a year later.

      Maybe we can have a static code analysis tool that helps us keep the codebase alive free of dead code.

        This is the controller panel for Smart Panels app

            [OPT-2753] Automatically identify dead code

            Omran Abazeed added a comment -

            This ticket was migrated to github: https://github.com/camunda/camunda-optimize/issues/10543. 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/10543 . Please use this link for any future references and continue any discussion there.

              Unassigned Unassigned
              sebastian.stamm Sebastian Stamm
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: