If a JSX expression takes up more than one line you must ...

If a JSX expression takes up more than one line you must ...

• A. You must wrap the multi-line expression in parentheses.
• B. You must place a semicolon at the end of the last line.
• C. You cannot use multi-line JSX expressions.
• D. You should split into multiple lines without any wrappers.

Answer: (A)

Wrapping a multi-line JSX expression in parentheses ensures it’s treated as a single expression by the JavaScript parser. This prevents JavaScript’s automatic semicolon insertion from prematurely ending the return, which can happen when a line break occurs right after return and the expression isn’t visibly grouped. The parentheses clearly group the entire JSX block, making the intended returned value unambiguous and reliable. In practice, you’ll often see: return ( <div> <span>Hello</span> </div> ); That guarantees the whole block is returned as one unit. The other ideas aren’t required or safe: you don’t have to or should add a semicolon at the end of the last line, you can use multi-line JSX, and splitting without wrappers can introduce parsing or runtime issues.

Wrapping a multi-line JSX expression in parentheses ensures it’s treated as a single expression by the JavaScript parser. This prevents JavaScript’s automatic semicolon insertion from prematurely ending the return, which can happen when a line break occurs right after return and the expression isn’t visibly grouped. The parentheses clearly group the entire JSX block, making the intended returned value unambiguous and reliable.

In practice, you’ll often see:

return (

Hello

);

That guarantees the whole block is returned as one unit. The other ideas aren’t required or safe: you don’t have to or should add a semicolon at the end of the last line, you can use multi-line JSX, and splitting without wrappers can introduce parsing or runtime issues.