Uploaded image for project: 'Stripes'
  1. Stripes
  2. STRIPES-137

Make redux state-change logging optional

    XMLWordPrintable

Details

    • New Feature
    • Status: Closed (View Workflow)
    • P3
    • Resolution: Done
    • None
    • None
    • None

    Description

      At present, the JavaScript console of Stripes applications is swamped by redux state-change logging messages of the form

      action @ 13:53:22.415 FOLIO_SAMPLE_MODULES_UI_USERS_USERS_FETCH_START core.js:111 
          prev state Object {okapi: Object, form: Object, @folio-sample-modules/ui-users-searchResults: Array[1], @folio-sample-modules/ui-users_user: Array[0], @folio-sample-modules/ui-users_users: Array[10]…} core.js:115
          action Object {data: undefined, type: "FOLIO_SAMPLE_MODULES_UI_USERS_USERS_FETCH_START"} core.js:123
          next state Object {okapi: Object, form: Object, @folio-sample-modules/ui-users-searchResults: Array[1], @folio-sample-modules/ui-users_user: Array[0], @folio-sample-modules/ui-users_users: Array[10]…} Users.js:166 
      

      Most of the whole, these are of no interest, and obscure more important logging. We should make them configuable.

      TestRail: Results

        Attachments

          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 - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 1 day
                  1d

                  TestRail: Runs

                    TestRail: Cases