Add section to usage guide on working with non-serializable data (#623)

* Adds section to usage guide on how to allow non-serializable values, updates error message in serializableStateInvariantMiddleware to link to new section in usage guide

* fix syntax error

* fixes

* update tests

* remove space at line ending

Co-authored-by: Lenz Weber <mail@lenzw.de>

Author: cloeper

docs/usage/usage-guide.md

@@ -1021,3 +1021,18 @@ export const usersAdapter = createEntityAdapter({
   sortComparer: (a, b) => a.first_name.localeCompare(b.first_name)
 })
 ```
+
+## Working with Non-serializable Data
+
+Occasionally, you may have actions that need to accept non-serializable data. This should be done very rarely and only if necessary. These non-serializable payloads shouldn't ever make it into your application state through a reducer. However, if you're using libraries such as redux saga or you're using middleware that could reasonably use non-serializable data you'll want to do the following:
+
+```js
+configureStore({
+  //...
+  middleware: getDefaultMiddleware({
+    serializableCheck: {
+      ignoredActions: ['your/action']
+    }
+  })
+})
+```

src/serializableStateInvariantMiddleware.test.ts

@@ -111,7 +111,8 @@ describe('serializableStateInvariantMiddleware', () => {
       Take a look at the logic that dispatched this action:  Object {
         \\"type\\": Symbol(SOME_CONSTANT),
       } 
-      (See https://redux.js.org/faq/actions#why-should-type-be-a-string-or-at-least-serializable-why-should-my-action-types-be-constants)"
+      (See https://redux.js.org/faq/actions#why-should-type-be-a-string-or-at-least-serializable-why-should-my-action-types-be-constants) 
+      (To allow non-serializable values see: https://redux-toolkit.js.org/usage/usage-guide#working-with-non-serializable-data)"
     `)
   })
 
@@ -363,7 +364,8 @@ describe('serializableStateInvariantMiddleware', () => {
           },
           \\"type\\": \\"test\\",
         } 
-        (See https://redux.js.org/faq/actions#why-should-type-be-a-string-or-at-least-serializable-why-should-my-action-types-be-constants)"
+        (See https://redux.js.org/faq/actions#why-should-type-be-a-string-or-at-least-serializable-why-should-my-action-types-be-constants) 
+        (To allow non-serializable values see: https://redux-toolkit.js.org/usage/usage-guide#working-with-non-serializable-data)"
       `)
     })
 

src/serializableStateInvariantMiddleware.ts

@@ -176,7 +176,8 @@ export function createSerializableStateInvariantMiddleware(
           value,
           '\nTake a look at the logic that dispatched this action: ',
           action,
-          '\n(See https://redux.js.org/faq/actions#why-should-type-be-a-string-or-at-least-serializable-why-should-my-action-types-be-constants)'
+          '\n(See https://redux.js.org/faq/actions#why-should-type-be-a-string-or-at-least-serializable-why-should-my-action-types-be-constants)',
+          '\n(To allow non-serializable values see: https://redux-toolkit.js.org/usage/usage-guide#working-with-non-serializable-data)'
         )
       }
     })