Skip to content

Conversation

@5ZYSZ3K
Copy link
Collaborator

@5ZYSZ3K 5ZYSZ3K commented Oct 17, 2025

This is a follow up to: #13, just made with a source branch from this repo, to b able to preview targeting PRs in one place

Description

This PR is meant to move the contents of react-native-render-html to this library with no other changes

Ultimately I decided to move packages/render-html and apps directories to the repo

  • packages/render-html contains the core logic of react-native-render-html
  • apps contains testing applications that may be helpful

I plan to create pull requests based off of this one to actually get it to work

References

Repository merge with history guide: https://gfscott.com/blog/merge-git-repos-and-keep-commit-history/
react-native-render-html repo: https://github.com/meliorence/react-native-render-html

Repository merge with history guide: https://gfscott.com/blog/merge-git-repos-and-keep-commit-history/
react-native-render-html repo: https://github.com/meliorence/react-native-render-html

jsamr added 30 commits June 24, 2021 15:11
Useful to compute the collapsed top margin for each member of a `TNode`
list.
Useful for rendering individual nodes in isolation, e.g. in the
`renderItem` prop of a `FlatList`.
Avoid re-renders of children of interative / dynamic custom renderers.
Keys don't need to be handled deeper in the tree, only when returning
arrays of React nodes. This was a legacy of v5, where custom renderers
were functions. Now that any custom renderer is wrapped in a
`TNodeRenderer` which has its own key, there is no need to use this key
in custom renderers.
…nction

Using deep equality would cause massive performance issues for the `dom`
source type.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This kind of decision should be very deliberate; perhaps you have more technical context to share? To be clear, I'm not against it, I just want to understand the rationale.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's because pnp does not work with react-native applications, they simply do not run, see here: https://yarnpkg.com/features/pnp#when-creating-a-new-project

It wasn't an issue before, since there were no apps in the repo, but now we've decided that it probably is better to keep an example app (and the website) in the repository, to make the development easier. We put having sample apps in the repo over keeping yarn pnp

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thanks for the context!

@5ZYSZ3K 5ZYSZ3K force-pushed the chore/migrate-render-html-with-history branch from b0cc2d5 to bbe4cb1 Compare October 18, 2025 18:48
@codecov
Copy link

codecov bot commented Oct 18, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 99.30%. Comparing base (170da76) to head (9843a43).

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #14   +/-   ##
=======================================
  Coverage   99.30%   99.30%           
=======================================
  Files          57       57           
  Lines        1148     1153    +5     
  Branches      313      318    +5     
=======================================
+ Hits         1140     1145    +5     
  Misses          8        8           
Flag Coverage Δ
css-processor 100.00% <ø> (ø)
transient-render-engine 98.95% <ø> (+<0.01%) ⬆️

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.