fix(types): improve the accuracy of dispatcher inference

[tianzhich]

• fix: dispatcher has no parameters if payload defined as any type Typescript error occurred after upgrading the project to version 2.0 #936
• fix: improve the accuracy of dispatcher inference, for example to differentiate the optional argument with user-defined undefined type.

[tianzhich]

The building process was blocked by rollup because it throws some TS errors(these errors didn't appear in my local with ts@4.4.2), can you have a look? @semoal

I want to formate the types file and also add/amend the documents in the week after next. Next week is China's National Day.

[github-actions]

size-limit report 📦

Path	Size
./packages/core/dist/core.umd.production.min.js	1.46 KB (+2.47% 🔺)
./packages/immer/dist/immer.umd.production.min.js	127 B (+0.8% 🔺)
./packages/loading/dist/loading.umd.production.min.js	706 B (0%)
./packages/persist/dist/persist.umd.production.min.js	172 B (0%)
./packages/select/dist/select.umd.production.min.js	456 B (0%)
./packages/updated/dist/updated.umd.production.min.js	407 B (0%)
./packages/typed-state/dist/typed-state.umd.production.min.js	248 B (0%)

[semoal]

Feel free to merge when you feel comfortable with :)

[ardyfeb]

I still getting this issue on v2.1.1

export const beepModel = createModel<RootModel>()(
  {
    state: <BeepModel>{
      visible: false
    },
    reducers: {
      showBeep: (state): void => {
        state.visible = true
      },
      hideBeep: (state): void => {
        state.visible = false
      }
    },
  }
)

dispatch.beep.showBeep() // throws "Expected 2 arguments, but got 0."

But works when adding emtpy effects: {} on beepModel

[tianzhich]

@ardyfeb What's your ts version? You should update it to ^4.4.

[ardyfeb]

@tianzhich i using typescript ^4.4.3

[tianzhich]

Could you create a reproduce repo or sandbox? The codes you posted above works in our tests.