Skip to content

Instantly share code, notes, and snippets.

@ryanflorence
Last active February 14, 2019 23:35
Show Gist options
  • Save ryanflorence/be2c385d714a3352389e30bd68e710f0 to your computer and use it in GitHub Desktop.
Save ryanflorence/be2c385d714a3352389e30bd68e710f0 to your computer and use it in GitHub Desktop.
// how do I write this:
const Profile: React.FunctionComponent<ProfileProps> = ({ userId, navigate }) => {
console.log(navigate);
return <div>{userId}</div>;
}
// as this:
function Profile({ userId, navigate }) {
console.log(navigate);
return <div>{userId}</div>;
}
// I tried this:
function Profile({ userId, navigate }): React.FunctionComponent<ProfileProps> {
console.log(navigate);
return <div>{userId}</div>;
}
// and this:
function Profile<React.FunctionComponent<ProfileProps>>({ userId, navigate }){
console.log(navigate);
return <div>{userId}</div>;
}
// neither work.
// Also we can't just do function Profile(props: ProfileProps) {}
// because Profile can be passed to a HOC or a "component" prop
// and w/o the React.FunctionComponent stuff it fails the type checking
// on React.ComponentType
@jsfroth
Copy link

jsfroth commented Feb 13, 2019

I stumbled over this a few days ago, too. The typings come from DefinitelyTyped and require you to define a children prop. I think @sunify got it quite right, but I don't think that you need the as React.FC<ProfileProps>; part. The correct return type is React.ReactNode, but it should be infered.

type ProfileProps = {};

export default function Profile(
  props: ProfileProps & { children?: React.ReactNode }
) {
  return <div />;
}

If you do not want to allow children you can type children as undefined_

type ProfileProps = {};

export default function Profile(
  props: ProfileProps & { children?: undefined }
) {
  return <div />;
}

Looking at the types I think the children definition of DefinitelyTyped is to strict. As far as I understand them, they also disallow components with render props as children.

@soufDev
Copy link

soufDev commented Feb 13, 2019

const Profile: React.FC<ProfileProps> = ({ navigate, userId }: ProfileProps) => {
  console.log(navigate);
  return <div>{userId}</div>;
}

in my last project using Typescript with React I used this one

@artisonian
Copy link

artisonian commented Feb 13, 2019

const Profile: React.FunctionComponent<ProfileProps> = function Profile({ userId, navigate }) {
  console.log(navigate);
  return <div>{userId}</div>;
}

Also works, even though that's probably not what you want to do. From what I can tell, tsx doesn’t see to let you cast that function declaration using the prefix syntax.

@sunify
Copy link

sunify commented Feb 13, 2019

@artisonian nice solution

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment