there are a lot of places where we use PropsWithChildren, and it either...

• actually makes the type incorrect (because the component does not actually accept/use the children prop)
• splits the definition of the props type into two places ("here are most of the props this component takes, and oh btw it also takes children), making the code slightly harder to decipher

I propose that...

• PropsWithChildren should only be used ungenerically, when children?: ReactNode is the the only prop accepted by the component.
• If a component accepts any props other than children?: ReactNode, it must declare it's own props type, and not use PropsWithChildren