The library claims to support the following useful pattern (see document-title):
<DocumentMeta>
<Component />
</DocumentMeta>
Otherwise you're required to add a wrapping element and handle any styles it might need to help with layout, which is something I'd like to keep out of containers or routes.
<View>
<DocumentMeta />
<Component />
</View>
While there is some untested code in place to support this, we (Twitter) encountered a bug that arises from the JSON parse/stringify (your clone util) of props that contain unserializable data, e.g., Symbols or functions. I believe the current approach to cloning should collect only the props you're interested in.
The library claims to support the following useful pattern (see document-title):
Otherwise you're required to add a wrapping element and handle any styles it might need to help with layout, which is something I'd like to keep out of containers or routes.
While there is some untested code in place to support this, we (Twitter) encountered a bug that arises from the JSON parse/stringify (your
clone
util) of props that contain unserializable data, e.g., Symbols or functions. I believe the current approach to cloning should collect only the props you're interested in.