TSX templates: Reconsider React.FC convention for component declarations

[ihabadham]

All TSX generator templates currently use React.FC<Props> for component declarations:

const HelloWorld: React.FC<HelloWorldProps> = (props) => {
const HelloServer: React.FC<HelloServerProps> = ({ name = 'World' }) => {
const HelloWorldApp: FC<HelloWorldAppProps> = (props) => {

This is consistent across the codebase (every TSX template follows it), but React.FC has been discouraged by parts of the React community for several years.

Historical argument (now resolved): React.FC used to implicitly include children in props, leading to unexpected behavior. This was fixed in @types/react v18 — React.FC no longer includes children.

Remaining arguments against React.FC:

• Makes return type implicit (always ReactElement | null)
• More verbose than a plain typed function
• Makes generic components harder to write
• The React TypeScript Cheatsheet recommends plain functions
• React's own documentation uses plain function declarations

Arguments for keeping React.FC:

• It's consistent across the entire codebase today
• Provides implicit return type checking
• For simple generator example components, the drawbacks are minimal
• Changing it would touch every TSX template

Not urgent or blocking. The convention works fine as-is. Just flagging for future consideration when the team next touches TSX templates.

Found during PR #2284 code review.

References:

• DefinitelyTyped PR #56210: Remove children from React.FC
• React TypeScript Cheatsheet: Function Components
• Related discussion on GitHub