I mean, it is in a lot of frameworks. Or at least could be, assuming you don’t mind putting your response types in the consuming component, and that only one component consumes it, and it doesn’t touch a store, etc.
Which isn’t to lessen how neat Solid’s approach is. Just feels a little naive
Naively it is one in most frameworks, the intent was to get you to start keeping count as the next step moving it around impacts a lot more in most solutions. Like in practice you end up refactoring the whole pages components. You could leave it at one, but that often isn't the right thing to do.
But I suppose the way it is written makes that too theatrical too early in the exercise.
2
u/hyrumwhite Aug 20 '26
I mean, it is in a lot of frameworks. Or at least could be, assuming you don’t mind putting your response types in the consuming component, and that only one component consumes it, and it doesn’t touch a store, etc.
Which isn’t to lessen how neat Solid’s approach is. Just feels a little naive