fix(react): process falsy values with JSX semantics

[thekip]

Description

Fixes #1904

Despite this is not marked as breaking change, but i expect this may start to behave differently for some users, that's why base of this PR is "next"

Types of changes

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update
• Examples update

Fixes # (issue)

Checklist

• I have read the CONTRIBUTING and CODE_OF_CONDUCT docs
• I have added tests that prove my fix is effective or that my feature works
• I have added the necessary documentation (if appropriate)

[vercel]

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

Name	Status	Preview	Comments	Updated (UTC)
js-lingui	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Apr 4, 2024 2:52pm

[github-actions]

size-limit report 📦

Path	Size
./packages/core/dist/index.mjs	2.86 KB (0%)
./packages/detect-locale/dist/index.mjs	723 B (0%)
./packages/react/dist/index.mjs	1.67 KB (0%)
./packages/remote-loader/dist/index.mjs	7.26 KB (0%)

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 77.06%. Comparing base (13f9ccb) to head (71027a9).
Report is 1 commits behind head on next.

Additional details and impacted files

@@            Coverage Diff             @@
##             next    #1906      +/-   ##
==========================================
- Coverage   77.18%   77.06%   -0.13%     
==========================================
  Files          84       84              
  Lines        2165     2158       -7     
  Branches      559      556       -3     
==========================================
- Hits         1671     1663       -8     
- Misses        381      382       +1     
  Partials      113      113              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[andrii-bodnar]

@thekip Is there a reason why this PR is targeting the next branch? If possible, it would be better to ship it in the v4 release

[thekip]

@thekip Is there a reason why this PR is targeting the next branch? If possible, it would be better to ship it in the v4 release

Despite this is not marked as breaking change, but i expect this may start to behave differently for some users, that's why base of this PR is "next"