fix: make models on init() Partial<T>

[semoal]

https://github.com/rematch/rematch/pull/891/files#diff-1f8711ffcf4ef0b26aea69d164072937102d5109ecfd8790b6e879c7421e00d3

Since I've checked how it's the strategy with typescript and addModel, has sense to define a RootModel which is Partial of a complete RootModel.

import { Models } from '@rematch/core'
import { players } from './players'
import { settings } from './settings'
import { cart } from './cart'

export interface RootModel extends Models<RootModel> {
	players: typeof players
	cart: typeof cart
	settings: typeof settings
}

export const models: Partial<RootModel> = { players, cart }

In this way we can define the complete typings but a FUTURE usage, but the current models isn't complete yet.

[github-actions]

size-limit report 📦

Path	Size
./packages/core/dist/core.umd.production.min.js	1.42 KB (0%)
./packages/immer/dist/immer.umd.production.min.js	143 B (0%)
./packages/loading/dist/loading.umd.production.min.js	596 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%)

[tianzhich]

I am still not sure why we need to partialize the defined rootModels. If we don't use this model, we should also remove its typing? Could you explain more clearly mate?

[tianzhich]

I seem to understand your opinion. Do you want to fix the dynamically added model's typing problem? I guess you want to define it's types before you add it dynamically. So there will no typing problem after it is added. Am I right?

[semoal]

I seem to understand your opinion. Do you want to fix the dynamically added model's typing problem? I guess you want to define it's types before you add it dynamically. So there will no typing problem after it is added. Am I right?

Exactly that

[tianzhich]

Well, I think that's well for dynamically adding features. Good job mate  👍