Skip to content

[typescript] Use ComponentType for more flexibility. #59

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

Merged
merged 1 commit into from
Oct 11, 2017
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions index.d.ts
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ import * as React from 'react';
* The configuration for an asynchronous component.
*/
export interface Configuration<P> {
resolve: () => Promise<React.Component<P>>;
resolve: () => Promise<React.ComponentType<P>>;
LoadingComponent?: (props: P) => JSX.Element;
ErrorComponent?: (props: P & { error: Error }) => JSX.Element;
name?: string;
Expand Down Expand Up @@ -40,7 +40,7 @@ export interface Context {
*
* @param config The configuration to use for the asynchronous component.
*/
export function asyncComponent<T extends React.Component<P>, P>(config: Configuration<P>): React.ComponentClass<P>;
export function asyncComponent<P>(config: Configuration<P>): React.ComponentType<P>;

/**
* Create a context for the asynchronous component resolving module.
Expand Down