typescript-react | Use TypeScript to develop react applications | Frontend Framework library

UPDATE — see @sgrove’s answer, he was awesome and helped me troubleshoot the issue!

okay, there were two options I had: (1) overwrite each enum converted from a string value representative of the __type previously or (2) hardcode these values in. To get the custom enum value I had to add the following to my codegen.yml:

BacklogItemDashboard is a function that returns a ReactElement. It is not a ReactElement itself.

Any of the following types describe a component which fixes your errors. Meaning that BacklogItemDashboard is assignable to this type and this type is assignable to the component prop of the Route component.

• () => ReactElement - a function which takes no argument and returns a React element.

• () => ReactElement | null - a function which takes no argument and returns a React element or null.

• React.FC - a function which takes no arguments except children and returns a React element or null.

• React.ComponentType - a function component or class component that takes no arguments except maybe children

• React.FC - a function component that takes the props provided by the Route

• React.ComponentType - a function component or class component that takes the props provided by the Router

I actually agree with the general premise of the "Why I Don't Use React.FC" article that you should type function arguments rather than the functions themselves when writing the function. I don't think that applies when you are talking about declaring the type for a prop which is a function, like component. I don't see any problem with using React.FC here. You don't need to change the type of BacklogItemDashboard as () => ReactElement is assignable to React.FC. But if you are opposed, you can go with () => ReactElement.

I am not sure, but I think you need to make the array a state too:

Try adding a jsconfig.json file in the root of the project with the following contents:

Ok, as per Package.json I think it was missing to install webpack-dev-server.

After I've done that, the error changed:

It's almost correct, but you forgot to apply connect(mapStateToProps, mapDispatchToProps) to your ChatAppComponent. This should work:

Here are some quick steps that should proly help:

• Go the /src folder
• And create this file chec-commerce.d.ts
  The d tells TypeScript that this is a declaration script.
• Inside the just created file, write this:

If you go to rambda compose typing you'll see that it's generic, so you can define what would be the resulting function, typing it like this removes the error

props.children === undefined because you're rendering