-
Notifications
You must be signed in to change notification settings - Fork 3
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
(WIP) Migrate render html #9
base: main
Are you sure you want to change the base?
Conversation
translateY: 'block', | ||
borderCurve: 'block', | ||
gap: 'block', | ||
inset: 'block', | ||
insetBlock: 'block', | ||
insetInline: 'block', | ||
marginBlock: 'block', | ||
marginInline: 'block', | ||
paddingBlock: 'block', | ||
paddingInline: 'block', | ||
objectFit: 'block' |
There was a problem hiding this comment.
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) |
There was a problem hiding this comment.
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.
"paths": { | ||
"@native-html/transient-render-engine": [ | ||
"./packages/transient-render-engine/src" | ||
], | ||
"@native-html/css-processor": ["./packages/css-processor/src"] | ||
} |
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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.
No description provided.