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
Currently this library provides bindings to DOM components but wraps it in ref forwarding and processes aria and data props in the constructor. This breaks compatibility with libs like helmet where the tool expects native components (it checks child.type against a set of tag names like title, meta etc.).
Would you be so kind and tell me if you think that an addition of something like DOM.Unwrapped which provides components based on a simple unsafeCreateDOMComponent tagName = unsafeCoerce tagName without ref forwarding and props processing is a good idea?
The text was updated successfully, but these errors were encountered:
Thanks again for building react-basic!
Currently this library provides bindings to DOM components but wraps it in ref forwarding and processes
aria
anddata
props in the constructor. This breaks compatibility with libs like helmet where the tool expects native components (it checkschild.type
against a set of tag names liketitle
,meta
etc.).Would you be so kind and tell me if you think that an addition of something like
DOM.Unwrapped
which provides components based on a simpleunsafeCreateDOMComponent tagName = unsafeCoerce tagName
without ref forwarding and props processing is a good idea?The text was updated successfully, but these errors were encountered: