Glad to see you! I know how you feel about lodash.set which is used in redux-persist-transform-filter can be vulnerable to prototype pollution, especially when considering the cases when object assignment uses Object.create(). But don’t worry because there is an easy method that can help you get rid of this method when saving user filters by making use of the following.

First, let’s define the saveUserFilter function. This function will manually filter the user state to include only the properties you need: username, displayName, and timeZone.

Here’s how you can do it:

import { createTransform } from 'redux-persist';

const saveUserFilter = createTransform(
  // Transform state before it's serialized and persisted.
  (inboundState, key) => {
    if (key === 'user') {
      // Only include specific properties in the persisted state.
      const { username, displayName, timeZone } = inboundState;
      return { username, displayName, timeZone };
    }
    return inboundState;
  },
  // Transform state being rehydrated.
  (outboundState, key) => {
    return outboundState;
  },
  // Specify which reducer this transform applies to.
  { whitelist: ['user'] }
);

const persistConfig = {
  key: 'root',
  storage,
  whitelist: ['user', 'timeZones'],
  transforms: [saveUserFilter],
};

export default persistConfig;

Explanation:

1. Create Transform: We’re using redux-persist‘s createTransform to define a custom transformation.
2. Inbound State: This part filters the state before it’s saved. We’re only keeping the properties (username, displayName, timeZone) we need from the user state.
3. Outbound State: This just returns the state as it is when it’s rehydrated.
4. Whitelist: We specify the user reducer in the whitelist so that this transform is applied only to it.

For more details on creating transforms with redux-persist, you can check out the official documentation.

Feel free to reach out if you have any more questions or need further help. Good luck with your project!