{aggregate.name}
;\n};\n```\n\nThanks to the magic of Redux, pushing a new event to an aggregate will only trigger re-renders of components hooked to the said aggregate. The same goes when listing aggregate ids: Only creating a new aggregate will trigger a re-render.\n\n### Configure with another store\n\nIf you already use Redux, you can merge the Castore Redux store with your own.\n\nFirst, know that event stores events are stored as Redux \"slices\". Their name is their `eventStoreId`, prefixed by a customizable string (`@castore` by default).\n\nYou can use the `getCastoreReducers` util to generate the Castore Redux reducers, and merge them with your own:\n\n```tsx\nimport { Provider } from 'react-redux';\n\nimport {\n ReduxEventStorageAdapter,\n getCastoreReducers,\n} from '@castore/redux-event-storage-adapter';\n\nconst castoreReducers = getCastoreReducers({\n eventStores: [pokemonsEventStore, trainersEventStore],\n // 👇 Optional\n prefix: 'customPrefix',\n});\n\nconst store = configureStore({\n reducer: {\n ...castoreReducers,\n customReducer,\n },\n});\n\n// 👇 Connect the event stores to the store\neventStores.forEach(eventStore => {\n eventStore.storageAdapter = new ReduxEventStorageAdapter({\n store,\n eventStoreId: eventStore.eventStoreId,\n // 👇 Don't forget the prefix if one has been provided\n prefix: 'customPrefix',\n });\n});\n\nconst MyReactApp = () => (\n