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

Replace redux-crud with our own actions and reducers.

    XMLWordPrintable

Details

    Description

      We brought in redux-crud as a convenience in stripes-connect to rapidly make actions and reducers available for common REST tasks. I'm surprised we've kept it around this long but it's always been more convenient to work around it so far.

      Ultimately though we'll need to build our own actions and reducers:

      • redux-crud tries to be a bit too clever for our purposes at times and so we wind up with mildly hacky things like the CLEAR action
      • it imposes limitations on the structure of the data we store
        • eg. it prevents us from choosing to include status data alongside records
      • it prevents us from using a more hierarchical structure for the Redux store
      • it will probably get in the way of later optimisations to reduce network traffic

      TestRail: Results

        Attachments

          Issue Links

            blocks

            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

            Task - A task that needs to be done. STRIPES-238 Nest resources under a single key per module rather than using a module prefix

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

            Task - A task that needs to be done. STRIPES-187 Update or replace redux-crud

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

            Task - A task that needs to be done. STRIPES-199 Better names for Redux actions

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

            New Feature - New feature requests STRIPES-211 When a new record is created, the component should receive props describing it

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

            Task - A task that needs to be done. STRIPES-262 support paging in stripes-connect

            • 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-425 Figure out how the `_cid` field appears in some record

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

            Activity

              People

                jason Jason Skomorowski
                jason Jason Skomorowski
                Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  Time Tracking

                    Estimated:
                    Original Estimate - Not Specified
                    Not Specified
                    Remaining:
                    Remaining Estimate - 0 minutes
                    0m
                    Logged:
                    Time Spent - 3 days, 5 hours, 45 minutes
                    3d 5h 45m

                    TestRail: Runs

                      TestRail: Cases