Collectives™ on Stack Overflow
Find centralized, trusted content and collaborate around the technologies you use most.
Learn more about Collectives
Teams
Q&A for work
Connect and share knowledge within a single location that is structured and easy to search.
Learn more about Teams
Ask Question
I'm working on a project with Typescript, React and Redux (all running in Electron), and I've run into a problem when I'm including one class based component in another and trying to pass parameters between them. Loosely speaking, I've got the following structure for the container component:
class ContainerComponent extends React.Component<any,any> {
render() {
const { propToPass } = this.props;
<ChildComponent propToPass={propToPass} />
export default connect(mapStateToProps, mapDispatchToProps)(ContainerComponent);
And the child component:
interface IChildComponentProps extends React.Props<any> {
propToPass: any
class ChildComponent extends React.Component<IChildComponentProps, any> {
export default connect(mapStateToProps, mapDispatchToProps)(ChildComponent);
Obviously I'm only including the basics and there is much more to both of these classes but I'm still getting an error when I try and run what looks to me like valid code. The exact error that I'm getting:
TS2339: Property 'propToPass' does not exist on type 'IntrinsicAttributes & IntrinsicClassAttributes<Component<{}, ComponentState>> & Readonly<{ childr...'.
When I first encountered the error I thought it was because I wasn't passing in an interface defining my props, but I created that (as you can see above) and it still doesn't work. I'm wondering, is there something I'm missing?
When I exclude the ChildComponent prop from the code in the ContainerComponent, it renders just fine (aside from my ChildComponent not having a critical prop) but with it in the JSX Typescript refuses to compile it. I think it might have something to do with the connect wrapping based on this article, but the problems in that article occurred in the index.tsx file and were a problem with the provider, and I'm getting my problems elsewhere.
So after reading through some related answers (specifically this one and this one and looking at @basarat's answer to the question, I managed to find something that works for me. It looks (to my relatively new React eyes) like Connect was not supplying an explicit interface to the container component, so it was confused by the prop that it was trying to pass.
So the container component stayed the same, but the child component changed a bit:
interface IChildComponentProps extends React.Props<any> {
... (other props needed by component)
interface PassedProps extends React.Props<any> {
propToPass: any
class ChildComponent extends React.Component<IChildComponentProps & PassedProps, any> {
export default connect<{}, {}, PassedProps>(mapStateToProps, mapDispatchToProps) (ChildComponent);
The above managed to work for me. Passing explicitly the props that the component is expecting from the container seemed to work and both components rendered properly.
NOTE: I know this is a very simplistic answer and I'm not exactly sure WHY this works, so if a more experienced React ninja wants to drop some knowledge on this answer I'd be happy to amend it.
–
What worked for me is simply changing the child Component type from React.FC to JSX.Element
Before (warning)
const Component: React.FC = () => {
After (no warning)
const Component = (): JSX.Element => {
Double check the newly added object types. When object type is not exactly as expected such error is thrown.
Ex. Type of props mentioned in component must match with type of props which are passed to that component.
–
In my case, I was building a typescript component that imported a component that was in javascript that uses connect.
Here was a quick way for me to fix the error.
// User is a javascript component
import _User from "./User";
// Inject types that this component accepts
const User = _User as unknown as React.JSXElementConstructor<{
userId: string
const UserProfile = () => {
const user = useCurrentUser();
return (
<div className="flex items-center justify-center">
<User userId={user.userId} />
Hope this helps you!
Make your child Component extend React.Component with the type you want or "any" type. ex: "extends React.Component<any> {...}"
export class ChildComponent extends React.Component<T> {
render() {
return (
<button className="square">
{this.props.value}
</button>
In Parent component you could then pass the value, ex:
renderSquare(i: Number) { return <ChildComponent value={i}/>; }
Check https://react-typescript-cheatsheet.netlify.app/docs/basic/getting-started/class_components/ for more info
Instead of export default connect(mapStateToProps, mapDispatchToProps)(ChildComponent);, prefer the connect decorator https://github.com/alm-tools/alm/blob/00f2f94efd3810af8a80a49f968c2ebdeb955399/src/app/fileTree.tsx#L136-L146
@connect((state: StoreState): Props => {
return {
filePaths: state.filePaths,
filePathsCompleted: state.filePathsCompleted,
rootDir: state.rootDir,
activeProjectFilePathTruthTable: state.activeProjectFilePathTruthTable,
fileTreeShown: state.fileTreeShown,
Where connect is defined here https://github.com/alm-tools/alm/blob/00f2f94efd3810af8a80a49f968c2ebdeb955399/src/typings/react-redux/react-redux.d.ts#L6-L36
Seems like the definitions you are using are probably out of date or invalid (perhaps poorly authored).
–
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.
