Details

    • Type: Improvement
    • Status: New
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 1.0
    • Fix Version/s: None
    • Component/s: Foundation
    • Labels:
      None

      Description

      Currently, each Target sub-class carries its own instance of an artifactType enum. Those enums all represent subsections of BaseArtifactEnum, providing only the values applicable to that targeted artifact type.

      While I understand the intent behind that setup, it tends to muck up the actual implementation (ex: not able to set the artifactType on any Target, without the use of reflection). Can we think of alternatives that would allow target type restrictions, but also use one single enum?

      Off the top of my head, I'm not sure what that would look like...

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              brmeyer Brett Meyer
            • Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated: