TS errors on 2.2.0 about rematch HOT 13 OPEN

This issue still exist :< It is a pity that this continues

from rematch.

Test looks good, though I'll see how I can extract the problem from my (admittedly large) repo onto a reproducible one.

from rematch.

Hello,
I've come across another issue using immer plugin which is fixed in the lates version. So I'm stuck between these 2 issues.

I've extracted a reproduction from my project here:
https://codesandbox.io/s/rematch-typescript-bug-b47q22?file=/src/App.tsx

Hope this helps fixing this one.

from rematch.

We'll look into it, as soon as possible. Thx for reporting this out, I thought we had an scenario of this on our testing suite.

from rematch.

Can't reproduce the issue with this test mate:

it('reducer without any argument', () => {
  const model = createModel<RootModel>()({
    state: 0,
    reducers: {
      inc(state) {
        return state
      },
    },
  })
  interface RootModel extends Models<RootModel> {
    myModel: typeof model
  }

  const store = init({ models: { myModel: model } })

  const { dispatch } = store
  dispatch.myModel.inc()
  // @ts-expect-error
  dispatch.myModel.inc(1)
})

Could you provide a sandbox?

from rematch.

1066936
Just pushed a commit to check against CI.

from rematch.

I'm finding the same trouble on 2.2.0 and not on 2.0.1 but not with a reducer but with a parameter-less effect.

from rematch.

I'm finding the same trouble on 2.2.0 and not on 2.0.1 but not with a reducer but with a parameter-less effect.

Hey Javi! Isn't this test

I'm open to help if i can reproduce it somehow

from rematch.

I recently ported my project from next.js to create-react-app. Strangely this issue is happening only in create-react-app for me.
I had to downgrade to v2.0.1

from rematch.

Do you use any plugins? or something we can use to reproduce it?

from rematch.

I have the same issue, probably caused by a similar bug in the argument typing calculation:

(property) setMark: (payload: any, meta: any) => any
Expected 2 arguments, but got 1.

my code:

dispatch.chartEditor.setMark("point")

I believe the reason is because I didn't have an effects entry in that particular model. When I added one (effects: (dispatch) => ({}) or effects: {}), the error goes away.

from rematch.

I have the same issue, probably caused by a similar bug in the argument typing calculation:

(property) setMark: (payload: any, meta: any) => any
Expected 2 arguments, but got 1.

my code:

dispatch.chartEditor.setMark("point")

I believe the reason is because I didn't have an effects entry in that particular model. When I added one (effects: (dispatch) => ({}) or effects: {}), the error goes away.

Our testing suite of typings, tests that scenario, so I guess it should be something else.

from rematch.

This issue happens when I build my project on nextjs but not on my vscode. Something really weird is happening.

from rematch.