feat(jsx): allow to merge CSSProperties declaration

[jonasnobile]

Type declarations don't allow to merge, so overriding type declaration from docs doesn't work for CSSProperties.

The author should do the following, if applicable

• Add tests
• Run tests
• bun run format:fix && bun run lint:fix to format the code
• Add TSDoc/JSDoc to document the code

[yusukebe]

Hi @jonasnobile

Nice! This is a good improvement. One thing: can you run bun run format:fix && bun run lint:fix to fixe the format?

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 96.21%. Comparing base (1fafc7a) to head (d68d109).
Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff            @@
##             main    #3228    +/-   ##
========================================
  Coverage   96.21%   96.21%            
========================================
  Files         151      151            
  Lines       15096    15096            
  Branches     2620     2756   +136     
========================================
  Hits        14524    14524            
  Misses        572      572            

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

[yusukebe]

Hi @jonasnobile

I've fixed the format myself. I'll merge this now. Thank you for your contribution!

[jonasnobile]

Hi @yusukebe,

Sorry, I've missed this one. Thanks for fixing formatting and merging it.

[nsaunders]

While converting the CSSProperties type alias to an interface is a welcome change, I am curious to know why it was necessary for the style prop to accept a string?

[EdamAme-x]

I'm not a specialist, but I'm sure it's not a problem in terms of compatibility.
Some properties can be used in a different direction than React.

[jonasnobile]

@nsaunders CSS properties could always be written as strings since {} inherently allows that. The change simply improves the typing when you choose to write styles as an object.