You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
where %S would be any of styles, {styles}, [styles], {[styles]}, {...styles}, [...styles].
These all render unstyled <Text> elements, with the correct amount of leading pound signs, like ### (so the rule works). Each <Text>'s style is an object with all (passed and default) styles keyed by element, like
Is all and not just applicable styles being passed to render a feature or a bug? If it's a feature, is there anything built in that would help with cases like this?
The text was updated successfully, but these errors were encountered:
here (typeof(node) === Object, Symbol(node) === Symbol([object Object]), node instanceof Object === true). Maybe type properties aren't carried over from my project not using Flow? If that's it, I can revisit with a PR later if you want. Only passing applicable styles to render, adding a distribution where Flow types are transpiled, or doing something else. Thanks!
Is there any preferred approach to preserve passed/default styles for matches when going through a rule?
In a rule for headings, I have
where
%S
would be any ofstyles
,{styles}
,[styles]
,{[styles]}
,{...styles}
,[...styles]
.These all render unstyled
<Text>
elements, with the correct amount of leading pound signs, like###
(so the rule works). Each<Text>
's style is an object with all (passed and default) styles keyed by element, likewhere something like
const unkeyedStyles = Object.keys(styles).map((key) => styles[key])
for%S
just applies all of them. Here's my current workaroundIs all and not just applicable styles being passed to
render
a feature or a bug? If it's a feature, is there anything built in that would help with cases like this?The text was updated successfully, but these errors were encountered: