Uploaded image for project: 'stripes-connect'
  1. stripes-connect
  2. STCON-1

Peer components with different dataKey should store separate data

    XMLWordPrintable

Details

    Description

      Jason and Jeremy came up with a nice solution to the multiple-instances-of-a-component problem described in STRIPES-320 and exemplified in STRIPES-293. At present, such components share the same data because their key in the Redux store is the same. We propose that if a component has a dataKey prop, then its value is included as part of the Redux-store key, so that in effect it has its own store. This will allow it to maintain its own data.

      TestRail: Results

        Attachments

          Issue Links

            blocks

            Task - A task that needs to be done. FOLIO-604 File some new issues on myself

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Bug - A problem which impairs or prevents the functions of the product. STCON-9 Components using this.props.resources do not work with dataKey

            • P1 - highest priority item, drop everything else before this is resolved, reserved for critical bugfixes
            • Closed

            Task - A task that needs to be done. STRIPES-293 Make a proof-of-concept joining component

            • P4 - lowest priority level, nice-to have things that require future discussion and design
            • Closed

            New Feature - New feature requests UIORG-18 Edit preferences for multiple plugins

            • P2 - normal priority level, must be included in the current development cycle
            • Closed
            is blocked by

            New Feature - New feature requests STCON-14 Module-level manifest

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Umbrella - STCON-18 status (and error, warn?) props for connected components

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            New Feature - New feature requests STCOR-21 Ability to show multiple separate instances of the Trivial module's <About> component

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Task - A task that needs to be done. STRIPES-433 Eliminate all uses of componentWillMount to provide initial values to resources

            • P2 - normal priority level, must be included in the current development cycle
            • Closed
            is duplicated by

            Bug - A problem which impairs or prevents the functions of the product. STCON-8 Data should be stored per-component, not per-module

            • P2 - normal priority level, must be included in the current development cycle
            • Closed
            relates to

            Task - A task that needs to be done. STCON-11 Get test-suite running again after STRPCONN-1 work

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            New Feature - New feature requests STCOR-18 In the Trivial module, add proof of concept for multiple instances with local resources

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Activity

              People

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

                Dates

                  Created:
                  Updated:
                  Resolved:

                  Time Tracking

                    Estimated:
                    Original Estimate - 0 minutes
                    0m
                    Remaining:
                    Time Spent - 1 week, 3 hours, 30 minutes Remaining Estimate - 3 hours
                    3h
                    Logged:
                    Time Spent - 1 week, 3 hours, 30 minutes Remaining Estimate - 3 hours
                    1w 3h 30m

                    TestRail: Runs

                      TestRail: Cases