Open bdudelsack opened 1 year ago
It is kinda of edge case, but the logic of the AutoClosingProcessor is too simple to handle this correctly.
AutoClosingProcessor
Source:
/* ... */ render( <BrowserRouter> <Routes> <Route path="/" element={<App />} /> <Route path="expenses" element={<Expenses />} /> <Route path="invoices" element={<Invoices />} /> </Routes> </BrowserRouter>, rootElement );
Rendered code:
/* ... */ render( <BrowserRouter> <Routes> <Route path="/" element={<App ></Route>} /> <Route path="expenses" element={<Expenses ></Route>} /> <Route path="invoices" element={<Invoices ></Route>} /> </Routes> </BrowserRouter>, rootElement );
The logic of the AutoClosingProcessor should include this case, because sometimes we pass Components as Attributes in React.
It is kinda of edge case, but the logic of the
AutoClosingProcessor
is too simple to handle this correctly.Source:
Rendered code:
The logic of the
AutoClosingProcessor
should include this case, because sometimes we pass Components as Attributes in React.