fix(types): allow using functions on the PropTypes (#9692) #9733
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ktsn
suggested changes
Mar 18, 2019
types/options.d.ts
Outdated
| @@ -144,7 +144,7 @@ export interface RenderContext<Props=DefaultProps> { | |||
| injections: any | |||
| } | |||
|
|
|||
| export type Prop<T> = { (): T } | { new(...args: any[]): T & object } | |||
| export type Prop<T> = { (): T } | { new(...args: any[]): T & object } | {new(...args: string[]): Function;} | |||
There was a problem hiding this comment.
Please unify the code style with existing one
{ new(...args: string[]): Function }
|
/cc @HerringtonDarkholme as you may be interested. |
ktsn
approved these changes
Mar 19, 2019
Kiku-Reise
pushed a commit
to Kiku-Reise/vue
that referenced
this issue
Jun 18, 2019
Lostlover
added a commit
to Lostlover/vue
that referenced
this issue
Dec 10, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
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:
devbranch for v2.x (or to a previous version branch), not themasterbranchfix #xxx[,#xxx], where "xxx" is the issue number)If adding a new feature, the PR's description includes:
Other information: