SignalType enumeration should be the same for Signal / Report / Baseline

XMLWordPrintable

    • Type: Improvement
    • Resolution: Fixed
    • Priority: Major
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Environment:

      Toby Considine

    • Hide

      Unify these Types into a single enumeration used for all Streams

      Show
      Unify these Types into a single enumeration used for all Streams
    • Hide

      Unify these Types into a single enumeration used for all Streams (applied in wd32)

      Show
      Unify these Types into a single enumeration used for all Streams (applied in wd32)

      There is already substantial overlap.
      Signals are request to Make It So. Reports are What did you make of it. Baselines are expectations about what it is.

      With the current structure of ItemBase / Payload, there is no barrier to using the same enumeration for all. I can think of use cases even for Price as a Baseline and as a Report.

            Assignee:
            William Cox (Inactive)
            Reporter:
            Toby Considine (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: