Redux Toolkit serializableCheck configuration when migrating from legacy Redux to RTK createSlice

When migrating a codebase from legacy Redux to Redux Toolkit's createSlice, the default serializableCheck middleware in configureStore begins to emit warnings for action payloads that contain non‑serializable values such as Date objects, class instances, or custom metadata.

The objective is to adjust the check so that it ignores those specific payloads (or particular action types) without disabling the middleware entirely, thereby preserving its ability to catch genuine serialization problems elsewhere in the store.

• How can the serializableCheck be configured to exclude certain action types (e.g., thunk‑generated actions) while keeping the check active for all other actions?
• Is there a supported way to whitelist specific payload shapes or nested state paths so that the check skips them but still validates the rest of the state tree?
• What pattern ensures that disabling the check for selected actions does not compromise Redux DevTools synchronization or persistence layers?