|
|
|
|
|
by dcherman
1872 days ago
|
|
Agreed, was typing a similar comment, however yours expressed that idea better than mine. Consider that this pattern contains N different properties that renders N different components (plus the default case), I don't know why you would want to put this into one component rather than having the consumer select the right one themselves. This even introduces the possibility of bugs - what happens if a consumer passes two sets of properties (which admittedly could be somewhat prevented by Typescript)? I don't really see the benefits of this approach for this particular example. |
|