Prevent new commands from using legacy command types

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Cluster Scalability
    • Fully Compatible
    • Cluster Scalability 2025-01-20
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      Any new commands added should use TypedCommand. However, a number of commands still use legacy defined types, so these definitions still exist - until we convert all commands to use TypedCommand, we can't actually remove the legacy definitions, and new commands are periodically added using the legacy types. In order to prevent this, we should create a way to prevent new commands from using legacy types (e.g. create a linter of some sort).

            Assignee:
            David Chen
            Reporter:
            Janna Golden
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: