fix: toHaveStyle nested arrays

[felippepuhle]

What:

Closes #109

Why:

ramda was removed on v4.0.11 which introduced a different behavior compared to what we had in the past, removing the ability of handling nested arrays as the style prop.

How:

Simply replacing mergeAllStyles by StyleSheet.flatten (from react-native itself)

Checklist:

• Documentation added to the
  docs (N/A)
• Typescript definitions updated (N/A)
• Tests
• Ready to be merged

[codecov]

Codecov Report

Merging #110 (682405b) into main (e628ca0) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##              main      #110   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            8         8           
  Lines          151       140   -11     
  Branches        51        44    -7     
=========================================
- Hits           151       140   -11     

Flag	Coverage Δ
node-14	100.00% <100.00%> (ø)
node-16	100.00% <100.00%> (ø)
node-18	100.00% <100.00%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files	Coverage Δ
src/utils.js	100.00% <ø> (ø)
src/to-have-style.js	100.00% <100.00%> (ø)

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

[mdjastrzebski]

Overall looks good. Seems like we could now completely remove mergeAll as it's not used anywhere else.

[mdjastrzebski]

Seems like I've found an issue with the existing behaviour in isSubset function, please take a look if my reasoning is sound.

[mdjastrzebski]

Looks good! I've updated the README.md examples to match current behavior.

[github-actions]

🎉 This PR is included in version 4.0.12 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[lokeshdangi]

hey. @felippepuhle
why was this test case removed from src/__tests__/to-have-style.js

expect(container).toHaveStyle({ transform: [{ rotate: '45deg' }] });

ideally this should also be present along with

expect(container).toHaveStyle({ transform: [{ scale: 2 }, { rotate: '45deg' }] });

to check if only a certain property in transform is present or not

[felippepuhle]

@lokeshdangi I brought up the same topic while changing to the suggested implementation, answer is here: #110 (comment)