Skip to content

(WIP) Migrate render html #9

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 13 commits into
base: main
Choose a base branch
from
Open

(WIP) Migrate render html #9

wants to merge 13 commits into from

Conversation

jsamr
Copy link
Contributor

@jsamr jsamr commented Nov 3, 2024

No description provided.

Comment on lines +46 to +56
translateY: 'block',
borderCurve: 'block',
gap: 'block',
inset: 'block',
insetBlock: 'block',
insetInline: 'block',
marginBlock: 'block',
marginInline: 'block',
paddingBlock: 'block',
paddingInline: 'block',
objectFit: 'block'
Copy link
Contributor Author

@jsamr jsamr Nov 4, 2024

Choose a reason for hiding this comment

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

@DorianMazur That won't work; this is due to the new react-native version supporting more of these props. But we need to implement the rules for each of these.

I suggest you instead:

  • suppress the error by adding as never after the object literal;
  • open a ticket to report the issue, I'll work on it;
  • add a comment referring to the ticket number, showing this is a momentarily hack.

? renderFn(assembledProps)
? renderFn(assembledProps as any)
Copy link
Contributor Author

Choose a reason for hiding this comment

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

@DorianMazur We prefer as never to as any (well we prefer none). This is immediate technical debt, please open a ticket and add a reference to this ticket in a comment to this line.

Comment on lines +9 to +14
"paths": {
"@native-html/transient-render-engine": [
"./packages/transient-render-engine/src"
],
"@native-html/css-processor": ["./packages/css-processor/src"]
}
Copy link
Contributor Author

Choose a reason for hiding this comment

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

@DorianMazur Can we scope this out of the PR? You should be fine as soon as you build each dependency manually. Since it is not a blocker, I suggest we address this in a separate PR; and discuss it as a single topic.

Copy link
Collaborator

Choose a reason for hiding this comment

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

Sure, I will remove it today.

@arasrezaei

This comment was marked as off-topic.

@native-html native-html locked as spam and limited conversation to collaborators Dec 27, 2024
@native-html native-html unlocked this conversation Apr 25, 2025
@5ZYSZ3K
Copy link

5ZYSZ3K commented Apr 28, 2025

@jsamr Do we want to keep the .yarn directory with its binary caches? Doesn't feel right tbh

Nevermind, I see now that yarn considers that as an endorsed approach
Sorry about that, as I've been working with yarn berry, we always had the nodeLinker: node-modules option

@5ZYSZ3K
Copy link

5ZYSZ3K commented Apr 28, 2025

@jsamr Maybe should all fixes and version upgrades in packages other than render-html be scoped out of it? What do you think?

Again, nevermind, I see that this PR contains general dependencies upgrade

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.

4 participants