Adjust key generating in the library

[5ZYSZ3K]

Closes #28

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 98.65%. Comparing base (acd9f87) to head (23b5fbf).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main      #29   +/-   ##
=======================================
  Coverage   98.65%   98.65%           
=======================================
  Files         140      140           
  Lines        2076     2083    +7     
  Branches      633      633           
=======================================
+ Hits         2048     2055    +7     
  Misses         27       27           
  Partials        1        1           

Flag	Coverage Δ
css-processor	100.00% <ø> (ø)
render	97.84% <100.00%> (+0.01%)	⬆️
transient-render-engine	98.95% <100.00%> (ø)

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

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

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[5ZYSZ3K]

@jsamr I've checked the usage of nodeIndex, and it seems like the only thing that could break because of that is removing top and bottom margins in <li> components, but I tested it and it seems like it's working fine

[5ZYSZ3K]

@jsamr By the way:
We've scheduled the first major release to this tuesday (this one won't be included). Would you be able to mark the react-native-render-html library as deprecated then?

[jsamr]

Thanks for spotting the bug
Ideally we would keep track of the parent key to avoid an ancestry traversal on each node, and just use it as a prefix.

Will still allow the fix, but there may be performance issues for very large trees. Would be awesome to follow up