PayloadAction with meta does not work

[SpaghettiC0des]

v1.3.0-alpha.8

Please check my example here

[phryneas]

The default behaviour of RTK is to create an action creator with only one argument and only a payload property. This behaviour cannot be modified by TS annotations, because TS annotations have no effect on runtime behaviour.

You can use the prepare notation to define a function that overrides this default behaviour.
This function has the same signature & behaviour as the prepare argument for createAction, so you can find most of the relevant documentation there.

In your specific case, you'd want something along the lines of

const cakeSlice = createSlice({
  name: 'cake',
  initialState,
  reducers: {
    fetchAll: {
      reducer(
        state,
        action: PayloadAction<Cake[], string, { currentPage: number }>
      ) {
        state.all = action.payload
        state.meta = action.meta
      },
      prepare(payload: Cake[], currentPage: number) {
        return { payload, meta: { currentPage } }
      }
    }
  }
})

PRs to make this more clear in the docs are always welcome!

[SpaghettiC0des]

My tsconfig

{
  "compilerOptions": {
    "resolveJsonModule": true,
    "target": "esnext",
    "module": "commonjs",
    "lib": [
      "es6"
    ],
    "allowJs": true,
    "jsx": "react-native",
    "noEmit": true,
    "incremental": true,
    "isolatedModules": true,
    "strict": true,
    "moduleResolution": "node",
    "baseUrl": "./src",
    "allowSyntheticDefaultImports": true,
    "esModuleInterop": true

  },
  "exclude": [
    "node_modules",
    "babel.config.js",
    "metro.config.js",
    "jest.config.js"
  ]
}

[phryneas]

Unfortunately, there's nothing wrong with that as well. Could you try to reproduce the problem in a codesandbox? Without something we can both access, it's just guesswork :/

[SpaghettiC0des]

@phryneas #350 and this comment fixed the problem. Thanks for your time!

[phryneas]

Please make sure to report accurate version information in the future.
I could have told you that from the beginning, but #350 was already a part of v1.3.0-alpha.8...