-
-
Notifications
You must be signed in to change notification settings - Fork 33.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: changed a type for AsyncComponentFactory component(fix #10252) #10253
base: dev
Are you sure you want to change the base?
fix: changed a type for AsyncComponentFactory component(fix #10252) #10253
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you add a test case for this?
It would be nice to also include in the commit body a reference to the issue Close #10252
a4f9d12
to
f75a39d
Compare
@posva added a test as requested 😅 |
@@ -26,7 +26,7 @@ export type AsyncComponentPromise<Data=DefaultData<never>, Methods=DefaultMethod | |||
) => Promise<Component | EsModuleComponent> | void; | |||
|
|||
export type AsyncComponentFactory<Data=DefaultData<never>, Methods=DefaultMethods<never>, Computed=DefaultComputed, Props=DefaultProps> = () => { | |||
component: AsyncComponentPromise<Data, Methods, Computed, Props>; | |||
component: Promise<Component | EsModuleComponent>; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
as @pikax noted, Data, Methods,... are not used anymore. Maybe we should pass them to Component
I've just spent a couple of hours trying to figure out what was wrong with my code and it turns out this was the problem... Any special reason this PR has not been merged yet? If by any chance the author isn't available anymore, is there any way I could take over this issue? |
000201 |
What kind of change does this PR introduce? (check at least one)
Does this PR introduce a breaking change? (check one)
If yes, please describe the impact and migration path for existing applications:
The PR fulfills these requirements:
dev
branch for v2.x (or to a previous version branch), not themaster
branchfix #xxx[,#xxx]
, where "xxx" is the issue number)If adding a new feature, the PR's description includes:
Other information:
Close #10252