Added comments to clarify key handling in jsx and createElement

[Ravi80595]

Summary

Added comments to clarify the handling of key in jsx and createElement.

• Explained why key can be reused in jsx since it always passes a new object.
• Noted that createElement might reuse the same props object, so assumptions about key reuse cannot be made.
• Updated comments to explain the current behavior of spreading keys causing warnings and noted future plans to retain spread keys while maintaining warnings.

How did you test this change?

• Code Review: Verified that the comments correctly describe the behavior by reviewing the relevant code sections.
• Testing: Ensured no functional changes were made by running the existing test suite and confirmed all tests passed.
• Alignment: Checked that the comments are consistent with the current and planned behavior for handling key.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
react-compiler-playground	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Sep 15, 2024 2:45am

[facebook-github-bot]

Hi @Ravi80595!

Thank you for your pull request and welcome to our community.

Action Required

In 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.

Process

In 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 CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks!