Uploaded image for project: 'stripes-smart-components'
  1. stripes-smart-components
  2. STSMACOM-491

Generalize the notion of "actuator" in <ControlledVocab>

    XMLWordPrintable

    Details

    • Type: New Feature
    • Status: Closed (View Workflow)
    • Priority: TBD
    • Resolution: Won't Do
    • Affects Version/s: None
    • Fix Version/s: None
    • Labels:
      None
    • Template:
    • Development Team:
      Thor

      Description

      When we needed to make <ControlledVocab> support Knowledge Integration’s “refdata” representation (for ReShare modules written using their non-RMB toolkit), I abstracted out the notion of “actuators” that would actually do the back-end CRUD operations — but instead of letting the caller provide its own actuators, I just let it choose between the two hardwired sets.

      I should generalise this so that you can either pick from a selection of provided actuators or provide your own. The latter would give us a way to generalise the CV UI for other purposes, e.g. maintaining a set of key-value pairs to be stashed as a single JSON object.

        TestRail: Results

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                mike Mike Taylor
                Reporter:
                mike Mike Taylor
                Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:

                    TestRail: Runs

                      TestRail: Cases