Client MVVM: Converter API with no component

XMLWordPrintable

    • Type: New Feature
    • Resolution: Unresolved
    • Priority: Normal
    • None
    • Affects Version/s: None
    • Component/s: None
    • Security Level: Jimmy
    • None
    • None

      User Story

      When using Converter in Client MVVM, we should not control component
      Currently it might confuse user to use it.

      Acceptance Criteria

      Provide a compatible Converter API with no Component version
      Do overloading and for compatible, should use default implementation in Interface

            Assignee:
            Unassigned
            Reporter:
            DevChu
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: