adamstep
commented
2 years ago One other approach we could consider is to allow <styles> elements anywhere within the XML. This could make it easier for one-off styling sometimes needed for a specific component.
Another question: should <styles> elements override global settings, or only apply to the scope (fragment or doc)? I can see benefits of using localized-styles rather than merging the global styles. RN makes this easy to implement by passing multiple stylesheets as the prop.
flochtililoch
Right now, the styles definition is represented under the
element.<styles>element, which by spec requires to be an immediate children of the<screen>element. Hyperview fragments by spec only return elements that can be appended to aProposal: define a new
<fragment>element, modeled after the<screen>element, that will serve the purpose of nesting content and styles in two separate elements. For example:We would need for this to update the existing parsing code to change the validation logic while preserving support for the old format, then extract the stylesheet here (like it's done here) and merge it in the existing stylesheet (stored on the React state).