Mixing
Correct Typing for HigherOrderComponents with recompose and typescript
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
I'm currently trying to get recompose into my react codebase. Therefore I was trying to get some basic things working, and I got it working, but I'm not really sure, if this is the correct way recompose is intended to work.
So I have following Code:
interface Value {
value: string
}
interface Loading {
loading: boolean
}
const TestComponent = (props: Value) => <div>Value: {props.value}</div>
const LoadingComponent = () => <div>Loading ...</div>
So I have a TestComponent, which should display the Value provided in the props, and additionaly I have a LoadingComponent, which should be shown, when the loading props is set.
So I used the branch function of recompose
const withLoading = branch<Loading>(
({loading}) => loading,
renderComponent(LoadingComponent)
)
Now when I use withLoadingon any Component without props I can set the loading prop on them.
const EnhancedCompWithLoading = withLoading(SomeCompWithoutProps)
render() {
return <EnhancedCompWithLoading loading={this.state.loading} />
}
This works fine for me, the real problem starts when trying to use this with Components with props. When I try it like this:
const TestWithLoading = withLoading(TestComponent)
render() {
return <TestWithLoading value="testVal" loading={this.state.loading} />
}
I get the ErrorMessage TS2339: Property 'value' does not exist on type 'IntrinsicAttributes & IntrinsicClassAttributes<Component<Loading, any, any>>
& Readonly<{ children?: ReactNode; }> & Readonly<Loading>'.
So I looked the type definition in @types/recompose up. branch<TOutter> returns a ComponentEnhancer<any,TOutter>. Which I understand, I want to be able to provide any component, and the <TOutter> generic is so, that the resulting component knows about the needed props for the test function. Thats also working without additionals props.
However the TypeDefinition for the ComponentEnhancer looks like this (recompose 0.30.2):
interface ComponentEnhancer<TInner, TOutter> {
(component: Component<TInner>): ComponentClass<TOutter>
}
So, the ComponentEnhancer<any, Loading> which I received from the previous branch function will return a ComponentClass<Loading>. However the <TInner> of the component I provide to the ComponentEnhancer will be thrown away and I cant use my Value props in the Enhanced Component.
So my Question here is, am i doing it just wrong, is there a better way to achieve this (with recompose). Or is it just a Bug in the TypeDeclaration, since changing the return of the ComponentEnhancer to ComponentClass<TOutter & TInner> fixes the whole thing for me.
Any thoughts about this?
javascript reactjs typescript recompose
asked Jan 3 at 15:25
AzaelAzael
286214
add a comment |
I'm currently trying to get recompose into my react codebase. Therefore I was trying to get some basic things working, and I got it working, but I'm not really sure, if this is the correct way recompose is intended to work.
So I have following Code:
interface Value {
value: string
}
interface Loading {
loading: boolean
}
const TestComponent = (props: Value) => <div>Value: {props.value}</div>
const LoadingComponent = () => <div>Loading ...</div>
So I have a TestComponent, which should display the Value provided in the props, and additionaly I have a LoadingComponent, which should be shown, when the loading props is set.
So I used the branch function of recompose
const withLoading = branch<Loading>(
({loading}) => loading,
renderComponent(LoadingComponent)
)
Now when I use withLoadingon any Component without props I can set the loading prop on them.
const EnhancedCompWithLoading = withLoading(SomeCompWithoutProps)
render() {
return <EnhancedCompWithLoading loading={this.state.loading} />
}
This works fine for me, the real problem starts when trying to use this with Components with props. When I try it like this:
const TestWithLoading = withLoading(TestComponent)
render() {
return <TestWithLoading value="testVal" loading={this.state.loading} />
}
I get the ErrorMessage TS2339: Property 'value' does not exist on type 'IntrinsicAttributes & IntrinsicClassAttributes<Component<Loading, any, any>>
& Readonly<{ children?: ReactNode; }> & Readonly<Loading>'.
So I looked the type definition in @types/recompose up. branch<TOutter> returns a ComponentEnhancer<any,TOutter>. Which I understand, I want to be able to provide any component, and the <TOutter> generic is so, that the resulting component knows about the needed props for the test function. Thats also working without additionals props.
However the TypeDefinition for the ComponentEnhancer looks like this (recompose 0.30.2):
interface ComponentEnhancer<TInner, TOutter> {
(component: Component<TInner>): ComponentClass<TOutter>
}
So, the ComponentEnhancer<any, Loading> which I received from the previous branch function will return a ComponentClass<Loading>. However the <TInner> of the component I provide to the ComponentEnhancer will be thrown away and I cant use my Value props in the Enhanced Component.
So my Question here is, am i doing it just wrong, is there a better way to achieve this (with recompose). Or is it just a Bug in the TypeDeclaration, since changing the return of the ComponentEnhancer to ComponentClass<TOutter & TInner> fixes the whole thing for me.
Any thoughts about this?
javascript reactjs typescript recompose
asked Jan 3 at 15:25
AzaelAzael
286214
add a comment |
I'm currently trying to get recompose into my react codebase. Therefore I was trying to get some basic things working, and I got it working, but I'm not really sure, if this is the correct way recompose is intended to work.
So I have following Code:
interface Value {
value: string
}
interface Loading {
loading: boolean
}
const TestComponent = (props: Value) => <div>Value: {props.value}</div>
const LoadingComponent = () => <div>Loading ...</div>
So I have a TestComponent, which should display the Value provided in the props, and additionaly I have a LoadingComponent, which should be shown, when the loading props is set.
So I used the branch function of recompose
const withLoading = branch<Loading>(
({loading}) => loading,
renderComponent(LoadingComponent)
)
Now when I use withLoadingon any Component without props I can set the loading prop on them.
const EnhancedCompWithLoading = withLoading(SomeCompWithoutProps)
render() {
return <EnhancedCompWithLoading loading={this.state.loading} />
}
This works fine for me, the real problem starts when trying to use this with Components with props. When I try it like this:
const TestWithLoading = withLoading(TestComponent)
render() {
return <TestWithLoading value="testVal" loading={this.state.loading} />
}
I get the ErrorMessage TS2339: Property 'value' does not exist on type 'IntrinsicAttributes & IntrinsicClassAttributes<Component<Loading, any, any>>
& Readonly<{ children?: ReactNode; }> & Readonly<Loading>'.
So I looked the type definition in @types/recompose up. branch<TOutter> returns a ComponentEnhancer<any,TOutter>. Which I understand, I want to be able to provide any component, and the <TOutter> generic is so, that the resulting component knows about the needed props for the test function. Thats also working without additionals props.
However the TypeDefinition for the ComponentEnhancer looks like this (recompose 0.30.2):
interface ComponentEnhancer<TInner, TOutter> {
(component: Component<TInner>): ComponentClass<TOutter>
}
So, the ComponentEnhancer<any, Loading> which I received from the previous branch function will return a ComponentClass<Loading>. However the <TInner> of the component I provide to the ComponentEnhancer will be thrown away and I cant use my Value props in the Enhanced Component.
So my Question here is, am i doing it just wrong, is there a better way to achieve this (with recompose). Or is it just a Bug in the TypeDeclaration, since changing the return of the ComponentEnhancer to ComponentClass<TOutter & TInner> fixes the whole thing for me.
Any thoughts about this?
javascript reactjs typescript recompose
asked Jan 3 at 15:25
AzaelAzael
286214
I'm currently trying to get recompose into my react codebase. Therefore I was trying to get some basic things working, and I got it working, but I'm not really sure, if this is the correct way recompose is intended to work.
So I have following Code:
interface Value {
value: string
}
interface Loading {
loading: boolean
}
const TestComponent = (props: Value) => <div>Value: {props.value}</div>
const LoadingComponent = () => <div>Loading ...</div>
So I have a TestComponent, which should display the Value provided in the props, and additionaly I have a LoadingComponent, which should be shown, when the loading props is set.
So I used the branch function of recompose
const withLoading = branch<Loading>(
({loading}) => loading,
renderComponent(LoadingComponent)
)
Now when I use withLoadingon any Component without props I can set the loading prop on them.
const EnhancedCompWithLoading = withLoading(SomeCompWithoutProps)
render() {
return <EnhancedCompWithLoading loading={this.state.loading} />
}
This works fine for me, the real problem starts when trying to use this with Components with props. When I try it like this:
const TestWithLoading = withLoading(TestComponent)
render() {
return <TestWithLoading value="testVal" loading={this.state.loading} />
}
I get the ErrorMessage TS2339: Property 'value' does not exist on type 'IntrinsicAttributes & IntrinsicClassAttributes<Component<Loading, any, any>>
& Readonly<{ children?: ReactNode; }> & Readonly<Loading>'.
So I looked the type definition in @types/recompose up. branch<TOutter> returns a ComponentEnhancer<any,TOutter>. Which I understand, I want to be able to provide any component, and the <TOutter> generic is so, that the resulting component knows about the needed props for the test function. Thats also working without additionals props.
However the TypeDefinition for the ComponentEnhancer looks like this (recompose 0.30.2):
interface ComponentEnhancer<TInner, TOutter> {
(component: Component<TInner>): ComponentClass<TOutter>
}
So, the ComponentEnhancer<any, Loading> which I received from the previous branch function will return a ComponentClass<Loading>. However the <TInner> of the component I provide to the ComponentEnhancer will be thrown away and I cant use my Value props in the Enhanced Component.
So my Question here is, am i doing it just wrong, is there a better way to achieve this (with recompose). Or is it just a Bug in the TypeDeclaration, since changing the return of the ComponentEnhancer to ComponentClass<TOutter & TInner> fixes the whole thing for me.
Any thoughts about this?
javascript reactjs typescript recompose
javascript reactjs typescript recompose
asked Jan 3 at 15:25
AzaelAzael
286214
asked Jan 3 at 15:25
AzaelAzael
286214
asked Jan 3 at 15:25
AzaelAzael
286214
asked Jan 3 at 15:25
AzaelAzael
286214
asked Jan 3 at 15:25
AzaelAzael
286214
286214
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
I am not familiar with branch and recompose but if this is just a typing issue we can fix it.
The problem is that the type for branch is not very good. If the intent is to forward the properties of the wrapped component to the HOC and add to the HOC the props typed explicitly to branch then a better type for the result would be:
type BetterComponentEnhancer<TOutter> = {
<TInner>(component: React.ComponentType<TInner>): React.ComponentClass<TInner & TOutter>
}
With this type, this will work:
const withLoading = branch<Loading>(
({ loading }) => loading,
renderComponent(LoadingComponent)
)as unknown as BetterComponentEnhancer<Loading>
type BetterComponentEnhancer<TOutter> = {
<TInner>(component: React.ComponentType<TInner>): React.ComponentClass<TInner & TOutter>
}
const TestWithLoading = withLoading(TestComponent)
function render() {
return <TestWithLoading value="testVal" loading={true} />
}
answered Jan 3 at 15:39
Titian Cernicova-DragomirTitian Cernicova-Dragomir
74.1k35370
Hm, thats basically what i wrote in my last two sentences. When changing the return type toComponentClass<TInner & TOutter>it will work. However I'm confused about theas unknownand why the<TInner>in Front of the BetterComponentEnhancer parameter
– Azael
Jan 3 at 15:45
@Azael wops, my bad missed the last line in the question, I madeBetterComponentEnhancera generic function to get the type of the props from the passed in component (TestComponent in this case) theas unkownis just a double type assertion as TS would not let me assert directly toBetterComponentEnhancer
– Titian Cernicova-Dragomir
Jan 3 at 15:49
So I tried your solution and it does work. Tooltip showsReact.ComponentClass<Value & Loading, any>. For Solution it wasReact.ComponentClass<any, any>. Still bit confused bout the TS Syntax there. I'll open an issue on the @types/recompose repo and will reference your solution.
– Azael
Jan 4 at 10:35
@Azael The syntax is just a generic function signature, it's pretty standard TS. If you open an issue please post it here as well, I would be interested to see the team's response
– Titian Cernicova-Dragomir
Jan 4 at 10:39
1
Sadly I still have no answer to the Issue ... However i'm using your solution, so i marked your answer as correct.
– Azael
Feb 10 at 22:26
|
show 1 more comment
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54025204%2fcorrect-typing-for-higherordercomponents-with-recompose-and-typescript%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
I am not familiar with branch and recompose but if this is just a typing issue we can fix it.
The problem is that the type for branch is not very good. If the intent is to forward the properties of the wrapped component to the HOC and add to the HOC the props typed explicitly to branch then a better type for the result would be:
type BetterComponentEnhancer<TOutter> = {
<TInner>(component: React.ComponentType<TInner>): React.ComponentClass<TInner & TOutter>
}
With this type, this will work:
const withLoading = branch<Loading>(
({ loading }) => loading,
renderComponent(LoadingComponent)
)as unknown as BetterComponentEnhancer<Loading>
type BetterComponentEnhancer<TOutter> = {
<TInner>(component: React.ComponentType<TInner>): React.ComponentClass<TInner & TOutter>
}
const TestWithLoading = withLoading(TestComponent)
function render() {
return <TestWithLoading value="testVal" loading={true} />
}
answered Jan 3 at 15:39
Titian Cernicova-DragomirTitian Cernicova-Dragomir
74.1k35370
Hm, thats basically what i wrote in my last two sentences. When changing the return type toComponentClass<TInner & TOutter>it will work. However I'm confused about theas unknownand why the<TInner>in Front of the BetterComponentEnhancer parameter
– Azael
Jan 3 at 15:45
@Azael wops, my bad missed the last line in the question, I madeBetterComponentEnhancera generic function to get the type of the props from the passed in component (TestComponent in this case) theas unkownis just a double type assertion as TS would not let me assert directly toBetterComponentEnhancer
– Titian Cernicova-Dragomir
Jan 3 at 15:49
So I tried your solution and it does work. Tooltip showsReact.ComponentClass<Value & Loading, any>. For Solution it wasReact.ComponentClass<any, any>. Still bit confused bout the TS Syntax there. I'll open an issue on the @types/recompose repo and will reference your solution.
– Azael
Jan 4 at 10:35
@Azael The syntax is just a generic function signature, it's pretty standard TS. If you open an issue please post it here as well, I would be interested to see the team's response
– Titian Cernicova-Dragomir
Jan 4 at 10:39
1
Sadly I still have no answer to the Issue ... However i'm using your solution, so i marked your answer as correct.
– Azael
Feb 10 at 22:26
|
show 1 more comment
I am not familiar with branch and recompose but if this is just a typing issue we can fix it.
The problem is that the type for branch is not very good. If the intent is to forward the properties of the wrapped component to the HOC and add to the HOC the props typed explicitly to branch then a better type for the result would be:
type BetterComponentEnhancer<TOutter> = {
<TInner>(component: React.ComponentType<TInner>): React.ComponentClass<TInner & TOutter>
}
With this type, this will work:
const withLoading = branch<Loading>(
({ loading }) => loading,
renderComponent(LoadingComponent)
)as unknown as BetterComponentEnhancer<Loading>
type BetterComponentEnhancer<TOutter> = {
<TInner>(component: React.ComponentType<TInner>): React.ComponentClass<TInner & TOutter>
}
const TestWithLoading = withLoading(TestComponent)
function render() {
return <TestWithLoading value="testVal" loading={true} />
}
answered Jan 3 at 15:39
Titian Cernicova-DragomirTitian Cernicova-Dragomir
74.1k35370
Hm, thats basically what i wrote in my last two sentences. When changing the return type toComponentClass<TInner & TOutter>it will work. However I'm confused about theas unknownand why the<TInner>in Front of the BetterComponentEnhancer parameter
– Azael
Jan 3 at 15:45
@Azael wops, my bad missed the last line in the question, I madeBetterComponentEnhancera generic function to get the type of the props from the passed in component (TestComponent in this case) theas unkownis just a double type assertion as TS would not let me assert directly toBetterComponentEnhancer
– Titian Cernicova-Dragomir
Jan 3 at 15:49
So I tried your solution and it does work. Tooltip showsReact.ComponentClass<Value & Loading, any>. For Solution it wasReact.ComponentClass<any, any>. Still bit confused bout the TS Syntax there. I'll open an issue on the @types/recompose repo and will reference your solution.
– Azael
Jan 4 at 10:35
@Azael The syntax is just a generic function signature, it's pretty standard TS. If you open an issue please post it here as well, I would be interested to see the team's response
– Titian Cernicova-Dragomir
Jan 4 at 10:39
1
Sadly I still have no answer to the Issue ... However i'm using your solution, so i marked your answer as correct.
– Azael
Feb 10 at 22:26
|
show 1 more comment
I am not familiar with branch and recompose but if this is just a typing issue we can fix it.
The problem is that the type for branch is not very good. If the intent is to forward the properties of the wrapped component to the HOC and add to the HOC the props typed explicitly to branch then a better type for the result would be:
type BetterComponentEnhancer<TOutter> = {
<TInner>(component: React.ComponentType<TInner>): React.ComponentClass<TInner & TOutter>
}
With this type, this will work:
const withLoading = branch<Loading>(
({ loading }) => loading,
renderComponent(LoadingComponent)
)as unknown as BetterComponentEnhancer<Loading>
type BetterComponentEnhancer<TOutter> = {
<TInner>(component: React.ComponentType<TInner>): React.ComponentClass<TInner & TOutter>
}
const TestWithLoading = withLoading(TestComponent)
function render() {
return <TestWithLoading value="testVal" loading={true} />
}
answered Jan 3 at 15:39
Titian Cernicova-DragomirTitian Cernicova-Dragomir
74.1k35370
I am not familiar with branch and recompose but if this is just a typing issue we can fix it.
The problem is that the type for branch is not very good. If the intent is to forward the properties of the wrapped component to the HOC and add to the HOC the props typed explicitly to branch then a better type for the result would be:
type BetterComponentEnhancer<TOutter> = {
<TInner>(component: React.ComponentType<TInner>): React.ComponentClass<TInner & TOutter>
}
With this type, this will work:
const withLoading = branch<Loading>(
({ loading }) => loading,
renderComponent(LoadingComponent)
)as unknown as BetterComponentEnhancer<Loading>
type BetterComponentEnhancer<TOutter> = {
<TInner>(component: React.ComponentType<TInner>): React.ComponentClass<TInner & TOutter>
}
const TestWithLoading = withLoading(TestComponent)
function render() {
return <TestWithLoading value="testVal" loading={true} />
}
answered Jan 3 at 15:39
Titian Cernicova-DragomirTitian Cernicova-Dragomir
74.1k35370
answered Jan 3 at 15:39
Titian Cernicova-DragomirTitian Cernicova-Dragomir
74.1k35370
answered Jan 3 at 15:39
Titian Cernicova-DragomirTitian Cernicova-Dragomir
74.1k35370
answered Jan 3 at 15:39
Titian Cernicova-DragomirTitian Cernicova-Dragomir
74.1k35370
74.1k35370
Hm, thats basically what i wrote in my last two sentences. When changing the return type toComponentClass<TInner & TOutter>it will work. However I'm confused about theas unknownand why the<TInner>in Front of the BetterComponentEnhancer parameter
– Azael
Jan 3 at 15:45
@Azael wops, my bad missed the last line in the question, I madeBetterComponentEnhancera generic function to get the type of the props from the passed in component (TestComponent in this case) theas unkownis just a double type assertion as TS would not let me assert directly toBetterComponentEnhancer
– Titian Cernicova-Dragomir
Jan 3 at 15:49
So I tried your solution and it does work. Tooltip showsReact.ComponentClass<Value & Loading, any>. For Solution it wasReact.ComponentClass<any, any>. Still bit confused bout the TS Syntax there. I'll open an issue on the @types/recompose repo and will reference your solution.
– Azael
Jan 4 at 10:35
@Azael The syntax is just a generic function signature, it's pretty standard TS. If you open an issue please post it here as well, I would be interested to see the team's response
– Titian Cernicova-Dragomir
Jan 4 at 10:39
1
Sadly I still have no answer to the Issue ... However i'm using your solution, so i marked your answer as correct.
– Azael
Feb 10 at 22:26
|
show 1 more comment
Hm, thats basically what i wrote in my last two sentences. When changing the return type toComponentClass<TInner & TOutter>it will work. However I'm confused about theas unknownand why the<TInner>in Front of the BetterComponentEnhancer parameter
– Azael
Jan 3 at 15:45
@Azael wops, my bad missed the last line in the question, I madeBetterComponentEnhancera generic function to get the type of the props from the passed in component (TestComponent in this case) theas unkownis just a double type assertion as TS would not let me assert directly toBetterComponentEnhancer
– Titian Cernicova-Dragomir
Jan 3 at 15:49
So I tried your solution and it does work. Tooltip showsReact.ComponentClass<Value & Loading, any>. For Solution it wasReact.ComponentClass<any, any>. Still bit confused bout the TS Syntax there. I'll open an issue on the @types/recompose repo and will reference your solution.
– Azael
Jan 4 at 10:35
@Azael The syntax is just a generic function signature, it's pretty standard TS. If you open an issue please post it here as well, I would be interested to see the team's response
– Titian Cernicova-Dragomir
Jan 4 at 10:39
1
Sadly I still have no answer to the Issue ... However i'm using your solution, so i marked your answer as correct.
– Azael
Feb 10 at 22:26
Hm, thats basically what i wrote in my last two sentences. When changing the return type to
ComponentClass<TInner & TOutter> it will work. However I'm confused about the as unknown and why the <TInner> in Front of the BetterComponentEnhancer parameter– Azael
Jan 3 at 15:45
Hm, thats basically what i wrote in my last two sentences. When changing the return type to
ComponentClass<TInner & TOutter> it will work. However I'm confused about the as unknown and why the <TInner> in Front of the BetterComponentEnhancer parameter– Azael
Jan 3 at 15:45
@Azael wops, my bad missed the last line in the question, I made
BetterComponentEnhancer a generic function to get the type of the props from the passed in component (TestComponent in this case) the as unkown is just a double type assertion as TS would not let me assert directly to BetterComponentEnhancer– Titian Cernicova-Dragomir
Jan 3 at 15:49
@Azael wops, my bad missed the last line in the question, I made
BetterComponentEnhancer a generic function to get the type of the props from the passed in component (TestComponent in this case) the as unkown is just a double type assertion as TS would not let me assert directly to BetterComponentEnhancer– Titian Cernicova-Dragomir
Jan 3 at 15:49
So I tried your solution and it does work. Tooltip shows
React.ComponentClass<Value & Loading, any>. For Solution it was React.ComponentClass<any, any>. Still bit confused bout the TS Syntax there. I'll open an issue on the @types/recompose repo and will reference your solution.– Azael
Jan 4 at 10:35
So I tried your solution and it does work. Tooltip shows
React.ComponentClass<Value & Loading, any>. For Solution it was React.ComponentClass<any, any>. Still bit confused bout the TS Syntax there. I'll open an issue on the @types/recompose repo and will reference your solution.– Azael
Jan 4 at 10:35
@Azael The syntax is just a generic function signature, it's pretty standard TS. If you open an issue please post it here as well, I would be interested to see the team's response
– Titian Cernicova-Dragomir
Jan 4 at 10:39
@Azael The syntax is just a generic function signature, it's pretty standard TS. If you open an issue please post it here as well, I would be interested to see the team's response
– Titian Cernicova-Dragomir
Jan 4 at 10:39
1
1
Sadly I still have no answer to the Issue ... However i'm using your solution, so i marked your answer as correct.
– Azael
Feb 10 at 22:26
Sadly I still have no answer to the Issue ... However i'm using your solution, so i marked your answer as correct.
– Azael
Feb 10 at 22:26
|
show 1 more comment
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54025204%2fcorrect-typing-for-higherordercomponents-with-recompose-and-typescript%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
