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

RFC: Think through re-usable card components for specific kinds of data

    XMLWordPrintable

Details

    • New Feature
    • Status: Closed (View Workflow)
    • TBD
    • Resolution: Done
    • None
    • None
    • Stripes Force

    Description

      Once we have the re-usable card component (STCOM-534), we're going to want to start using cards in lots of different displays, and many of them will be the same: for example, many different apps will need an Item card. How can we make a re-usable card for items, another for users, etc.?

      This is not really an issue for implementing, but for discussing the architectural implications. For example: where should such components live?

      • Each in its own package?
      • All in one new stripes-cards package?
      • In stripes-smart-components?
      • Each in the app that naturally "owns" that kind of data?

      The last of these is appealing, but then raises the question of how apps could best export such card components. And then we get into the notion of apps depending on other apps.

      (This is a sort-of-duplicate of an issue that I've been assigned in ReShare — https://openlibraryenvironment.atlassian.net/browse/PR-180 — but all the people I need to discuss this with are on the FOLIO tracker but not that one, hence this issue.)

      TestRail: Results

        Attachments

          Issue Links

            Activity

              People

                mike Mike Taylor
                mike Mike Taylor
                Votes:
                0 Vote for this issue
                Watchers:
                8 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases