docs: clarify conditional operator usage in JSX#8252
docs: clarify conditional operator usage in JSX#8252ChristopherJamesL wants to merge 1 commit intoreactjs:mainfrom
Conversation
|
Thank you for your pull request and welcome to our community. Action RequiredIn order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you. ProcessIn order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA. Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks! |
Size changesDetails📦 Next.js Bundle Analysis for react-devThis analysis was generated by the Next.js Bundle Analysis action. 🤖 This PR introduced no changes to the JavaScript bundle! 🙌 |
|
Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks! |
This PR improves the wording in the Learn > Quick Start section of the docs to clarify how conditional rendering works in JSX.
The previous text could be interpreted to mean that
ifcannot be used with JSX at all. This change clarifies that the conditional (? :) operator can be used inline inside JSX, which more accurately reflects how JSX expressions work.Fixes #8247