@@ -114,12 +114,12 @@ describe('serializableStateInvariantMiddleware', () => {
114114    store . dispatch ( dispatchedAction ) 
115115
116116    expect ( getLog ( ) . log ) . toMatchInlineSnapshot ( ` 
117-       "A non-serializable value was detected in an action, in the path: \`payload\`. Value: Symbol(SOME_CONSTANT) 
117+       "A non-serializable value was detected in an action, in the path: \`payload\`. Value: Symbol(SOME_CONSTANT)   
118118      Take a look at the logic that dispatched this action:  Object { 
119119        "payload": Symbol(SOME_CONSTANT), 
120120        "type": "an-action", 
121-       } 
122-       (See https://redux.js.org/faq/actions#why-should-type-be-a-string-or-at-least-serializable-why-should-my-action-types-be-constants) 
121+       }   
122+       (See https://redux.js.org/faq/actions#why-should-type-be-a-string-or-at-least-serializable-why-should-my-action-types-be-constants)   
123123      (To allow non-serializable values see: https://redux-toolkit.js.org/usage/usage-guide#working-with-non-serializable-data)" 
124124    ` ) 
125125  } ) 
@@ -158,7 +158,7 @@ describe('serializableStateInvariantMiddleware', () => {
158158    store . dispatch ( {  type : ACTION_TYPE  } ) 
159159
160160    expect ( getLog ( ) . log ) . toMatchInlineSnapshot ( ` 
161-       "A non-serializable value was detected in the state, in the path: \`testSlice.a\`. Value: Map {} 
161+       "A non-serializable value was detected in the state, in the path: \`testSlice.a\`. Value: Map {}   
162162      Take a look at the reducer(s) handling this action type: TEST_ACTION. 
163163      (See https://redux.js.org/faq/organizing-state#can-i-put-functions-promises-or-other-non-serializable-items-in-my-store-state)" 
164164    ` ) 
@@ -219,7 +219,7 @@ describe('serializableStateInvariantMiddleware', () => {
219219
220220      // since default options are used, the `entries` function in `serializableObject` will cause the error 
221221      expect ( getLog ( ) . log ) . toMatchInlineSnapshot ( ` 
222-         "A non-serializable value was detected in the state, in the path: \`testSlice.a.entries\`. Value: [Function entries] 
222+         "A non-serializable value was detected in the state, in the path: \`testSlice.a.entries\`. Value: [Function entries]   
223223        Take a look at the reducer(s) handling this action type: TEST_ACTION. 
224224        (See https://redux.js.org/faq/organizing-state#can-i-put-functions-promises-or-other-non-serializable-items-in-my-store-state)" 
225225      ` ) 
@@ -266,7 +266,7 @@ describe('serializableStateInvariantMiddleware', () => {
266266
267267      // error reported is from a nested class instance, rather than the `entries` function `serializableObject` 
268268      expect ( getLog ( ) . log ) . toMatchInlineSnapshot ( ` 
269-         "A non-serializable value was detected in the state, in the path: \`testSlice.a.third.bad-map-instance\`. Value: Map {} 
269+         "A non-serializable value was detected in the state, in the path: \`testSlice.a.third.bad-map-instance\`. Value: Map {}   
270270        Take a look at the reducer(s) handling this action type: TEST_ACTION. 
271271        (See https://redux.js.org/faq/organizing-state#can-i-put-functions-promises-or-other-non-serializable-items-in-my-store-state)" 
272272      ` ) 
@@ -371,14 +371,14 @@ describe('serializableStateInvariantMiddleware', () => {
371371      } ) . dispatch ( {  type : 'test' ,  meta : {  arg : nonSerializableValue  }  } ) 
372372
373373      expect ( getLog ( ) . log ) . toMatchInlineSnapshot ( ` 
374-         "A non-serializable value was detected in an action, in the path: \`meta.arg\`. Value: Map {} 
374+         "A non-serializable value was detected in an action, in the path: \`meta.arg\`. Value: Map {}   
375375        Take a look at the logic that dispatched this action:  Object { 
376376          "meta": Object { 
377377            "arg": Map {}, 
378378          }, 
379379          "type": "test", 
380-         } 
381-         (See https://redux.js.org/faq/actions#why-should-type-be-a-string-or-at-least-serializable-why-should-my-action-types-be-constants) 
380+         }   
381+         (See https://redux.js.org/faq/actions#why-should-type-be-a-string-or-at-least-serializable-why-should-my-action-types-be-constants)   
382382        (To allow non-serializable values see: https://redux-toolkit.js.org/usage/usage-guide#working-with-non-serializable-data)" 
383383      ` ) 
384384    } ) 
@@ -503,7 +503,7 @@ describe('serializableStateInvariantMiddleware', () => {
503503
504504    // testSlice.b.d was not covered in ignoredPaths, so will still log the error 
505505    expect ( getLog ( ) . log ) . toMatchInlineSnapshot ( ` 
506-       "A non-serializable value was detected in the state, in the path: \`testSlice.b.d\`. Value: Map {} 
506+       "A non-serializable value was detected in the state, in the path: \`testSlice.b.d\`. Value: Map {}   
507507      Take a look at the reducer(s) handling this action type: TEST_ACTION. 
508508      (See https://redux.js.org/faq/organizing-state#can-i-put-functions-promises-or-other-non-serializable-items-in-my-store-state)" 
509509    ` ) 
0 commit comments