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, we require converters to be defined to do anything. But as of React 16.x (if not earlier?), we can render custom/arbitrary tag names. This means that we can turn an XML document into a React tree without any provided converters.
You mean a constructor option to control whether or not we alert the library user of this issue? that makes sense. Naming the interface will be hardest. We'll have to do a bit of research I think.
Currently, we require converters to be defined to do anything. But as of React 16.x (if not earlier?), we can render custom/arbitrary tag names. This means that we can turn an XML document into a React tree without any provided converters.
e.g.
I'd like to propose that this be our default behavior.
The text was updated successfully, but these errors were encountered: