User story / Problem statement
Currently, WalletStatusVerifier types its children prop as ReactElement (WalletStatusVerifier.tsx:30), which forces consumers to wrap content in fragments and suppress lint warnings. Since the component is just a context provider, there is no reason to restrict children to ReactElement.
Expected outcome
Consumers can pass any valid React children (strings, fragments, arrays, null) without fragment wrappers or lint suppressions.
Acceptance criteria
User story / Problem statement
Currently,
WalletStatusVerifiertypes itschildrenprop asReactElement(WalletStatusVerifier.tsx:30), which forces consumers to wrap content in fragments and suppress lint warnings. Since the component is just a context provider, there is no reason to restrict children toReactElement.Expected outcome
Consumers can pass any valid React children (strings, fragments, arrays, null) without fragment wrappers or lint suppressions.
Acceptance criteria
children?: ReactElementtochildren?: ReactNodeinWalletStatusVerifierPropsReactElementconstraint