React.FC is now perfectly fine to use in TypeScript 5.1 and React 18. It no longer implicitly includes children and accepts more return types.

9 авг. 2022 г. · React.FC is unnecessary. Doubly so now that the React 18 types no longer automatically include children as a prop. The simplest approach is: Should FC still be used? : r/reactjs - Reddit Is the FC type still considered a bad practice? : r/reactjs - Reddit Should we use React.FC to provide type for Components? Другие результаты с сайта www.reddit.com

7 апр. 2022 г. · In React, children is a regular prop and is not something special. So you need to define it just like you define all the other props. TypeScript React.FC<Props> confusion - Stack Overflow Why "he" does not write React.FC on each function? Другие результаты с сайта stackoverflow.com

8 янв. 2023 г. · React.FC is a type that stands for "Function Component" in React. It is a generic type that allows you to specify the props that a function component will ...

As of TypeScript 5.1 and React 18, React.FC is now officially 'fine'. It no longer implicitly includes children in the props type. It no longer breaks if you ...

19 июн. 2023 г. · When you use React.FC , it implicitly includes children in the props, even if you don't need them. It means all components accept children ...

Facebook has removed React.FC from their base template for a TypeScript project. The reason for this was that it was found to be an unnecessary feature.

FunctionComponent (or the shorthand React.FC ) is not needed. If you're still using React 17 or TypeScript lower than 5.1, it is even discouraged. This is a ...

19 окт. 2021 г. · It is possible with React.FC to create compound components, but the typing makes the code unreadable fast.

30 июл. 2020 г. · React.FC types a function. That's in its name, function component. Function types are really hard to apply to regularly named functions.